Known issues: Difference between revisions

Known issues (view source)

625 bytes removed , 7 years ago

no edit summary

Bureaucrats, cc_docs_admin, cc_staff, rsnt_translations

2,837

edits

@@ Line 6: / Line 6: @@
 = Shared issues = <!--T:2-->
 * The status page at http://status.computecanada.ca/ is not updated automatically yet, so may lag in showing current status.
-* Utilization accounting is not currently being forwarded to the [https://ccdb.computecanada.ca Compute Canada database].
 == Scheduler issues == <!--T:6-->
-* Some users are experiencing excessively long wait times for jobs to run. Staff are analyzing the causes and plan to introduce scheduler changes in the next few weeks that should alleviate the problem. (16:48, 27 September 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]].
-* Slurm epilog does not fully clean up processes from ended jobs, especially if the job did not exit normally.
-** This has been greatly improved after the addition of the epilog.clean script, but there are still nodes occasionally marked down for epilog failure.
 * 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.