HP 1032 ClusterPack V2.4 Tutorial - Page 123

Check Queue status, Using the Clusterware Pro V5.1 Web Interface, Using the Clusterware Pro V5.1

Get HP 1032 PDF manuals and user guides View all HP 1032 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 123 highlights

2.3.3 Check Queue status Using the Clusterware Pro V5.1 Web Interface: From the Jobs tab: z Review the Queues table. Use the Previous and Next buttons to view more Queues. Using the Clusterware Pro V5.1 CLI: % bqueues [] References: z 3.7.8 How do I access the Clusterware Pro V5.1 Web Interface? z 3.7.9 How do I access the Clusterware Pro V5.1 Command Line Interface? Back to Top 2.3.4 Remove temporary files from Compute Nodes The process of removing temporary files created by an application can vary depending on whether the job was submitted to an AppRS queue or a non-AppRS LSF queue. Jobs submitted to an AppRS queue execute in temporary directories allocated by AppRS on each node where the job runs. AppRS copies the contents of these directories back to the host that the job was submitted from when the job completes. As long as the application only generates files within its execution directory, there is no need for the user to remove temporary files generated by an application. In the event AppRS restarts an application on a new set of nodes, the original working directories and files created before the migration are not removed. This is done in order to be as careful as possible about avoiding data loss. In addition, the files and directories on the unavailable host(s) cannot be removed at that time because the host cannot be reached. The user must manually remove these files using the AppRS commands apprs_ls and apprs_clean. Use apprs_ls to list the directories allocated by AppRS to the current user: % apprs_ls For non-root users, apprs_clean can only be used to remove files that belong to a specific job id. This protects files that are currently in use by another job from being accidentally erased. % apprs_clean root can delete all apprs related directories. This command should be used with great caution

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
2.3.3 Check Queue status
Using the Clusterware Pro V5.1 Web Interface:
From the Jobs tab:
Review the Queues table. Use the Previous and Next buttons to view more
Queues.
Using the Clusterware Pro V5.1 CLI:
%
bqueues [<queue_name>]
References:
3.7.8 How do I access the Clusterware Pro V5.1 Web Interface?
3.7.9 How do I access the Clusterware Pro V5.1 Command Line Interface?
Back to Top
2.3.4 Remove temporary files from Compute Nodes
The process of removing temporary files created by an application can vary depending on
whether the job was submitted to an AppRS queue or a non-AppRS LSF queue.
Jobs submitted to an AppRS queue execute in temporary directories allocated by AppRS on
each node where the job runs. AppRS copies the contents of these directories back to the host
that the job was submitted from when the job completes. As long as the application only
generates files within its execution directory, there is no need for the user to remove
temporary files generated by an application.
In the event AppRS restarts an application on a new set of nodes, the original working
directories and files created before the migration are not removed. This is done in order to be
as careful as possible about avoiding data loss. In addition, the files and directories on the
unavailable host(s) cannot be removed at that time because the host cannot be reached. The
user must manually remove these files using the AppRS commands apprs_ls and
apprs_clean. Use apprs_ls to list the directories allocated by AppRS to the current user:
%
apprs_ls
For non-root users, apprs_clean can only be used to remove files that belong to a specific job
id. This protects files that are currently in use by another job from being accidentally erased.
%
apprs_clean <jobid>
root can delete all apprs related directories. This command should be used with great caution