rsnt_translations
56,430
edits
Known issues: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
== Scheduler issues == <!--T:6--> | == Scheduler issues == <!--T:6--> | ||
* Interactive jobs started via <tt>salloc</tt> require X11 forwarding to be enabled when you connect to the cluster. On Linux and MacOS, you can typically enable X11 forwarding by adding the option <tt>-X</tt> or <tt>-Y</tt> to your <tt>ssh</tt> command. If you do not have X11 forwarding capabilities, you can use <tt>srun --pty bash</tt> as the command to be run by <tt>salloc</tt>. For example: <tt>salloc --time=1:00:00 --ntasks=1 srun --pty bash</tt> ( | * Interactive jobs started via <tt>salloc</tt> require X11 forwarding to be enabled when you connect to the cluster. On Linux and MacOS, you can typically enable X11 forwarding by adding the option <tt>-X</tt> or <tt>-Y</tt> to your <tt>ssh</tt> command. If you do not have X11 forwarding capabilities, you can use <tt>srun --pty bash</tt> as the command to be run by <tt>salloc</tt>. For example: <tt>salloc --time=1:00:00 --ntasks=1 srun --pty bash</tt>. (''Reported at 12:26, 13 December 2017 (UTC)'') | ||
* The CC Slurm configuration encourages whole-node jobs. When appropriate, users should request whole-node rather than per-core resources. See [[Job_scheduling_policies#Whole_nodes_versus_cores;|Job Scheduling - Whole Node Scheduling]]. | * The CC Slurm configuration encourages whole-node jobs. When appropriate, users should request whole-node rather than per-core resources. See [[Job_scheduling_policies#Whole_nodes_versus_cores;|Job Scheduling - Whole Node Scheduling]]. | ||
* By default, the job receives environment settings from the submitting shell. This can lead to irreproducible results if it's not what you expect. To force the job to run with a fresh-like login environment, you can submit with <tt>--export=none</tt> or add <tt>#SBATCH --export=NONE</tt> to your job script. | * By default, the job receives environment settings from the submitting shell. This can lead to irreproducible results if it's not what you expect. To force the job to run with a fresh-like login environment, you can submit with <tt>--export=none</tt> or add <tt>#SBATCH --export=NONE</tt> to your job script. | ||