Commit 1edef42c authored by Lisa Gerhardt's avatar Lisa Gerhardt

Added xfer queue and cleaned up language

parent 8997858a
......@@ -147,6 +147,14 @@ encounter problems due to firewalls at the client site. Often you will
have to configure your client firewall to allow connections to
HPSS. See the HPSS firewall page for more details.
#### Use the Xfer Queue
User the dedicated [xfer queue](../../jobs/examples/#xfer-queue) for
long-running transfers to / from HPSS. You can also submit jobs to the
xfer queue after your computations are done. The xfer queue is
configured to limit the number of running jobs per user to the same
number as the limit of HPSS sessions.
### Session Limits
Each HPSS user is limited to no more than 15 concurrent HPSS sessions.
......
......@@ -207,12 +207,13 @@ $$
The intended use of the xfer queue is to transfer data between Cori or
Edison and HPSS. The xfer jobs run on one of the login nodes and are
free of charge. If you want to transfer data to the HPSS
archive system at the end of a regular job, you can submit an xfer job at the
free of charge. If you want to transfer data to the HPSS archive
system at the end of a regular job, you can submit an xfer job at the
end of your batch job script via ```sbatch -M escori hsi put
<my_files>``` (use esedison on Edison), so that you will not get charged for the duration of the
data transfer. The xfer jobs can be monitored via “squeue -M
escori”.
<my_files>``` (use esedison on Edison), so that you will not get
charged for the duration of the data transfer. The xfer jobs can be
monitored via “squeue -M escori”. The number of running jobs for each
user is limited to the number of concurrent HPSS sessions (15).
!!! warn
Do not run computational jobs in the xfer queue.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment