Bureaucrats, cc_docs_admin, cc_staff
2,915
edits
RAC transition FAQ: Difference between revisions
Jump to navigation
Jump to search
adjust scheduler work plan
m (→Storage) |
(adjust scheduler work plan) |
||
| Line 14: | Line 14: | ||
=== Job scheduling === | === Job scheduling === | ||
* The scheduler team is planning to archive and compact the Slurm database on April | * The scheduler team is planning to archive and compact the Slurm database on April 3 before implementing the new allocations on April 4. We hope to schedule the archive and compaction during off-peak hours. During this time the database may be unresponsive. Specifically, <tt>sacct</tt> and <tt>sacctmgr</tt> may be unresponsive. | ||
* | * We expect to begin replacing 2018 allocations with 2019 allocations on April 4. | ||
* Job priority may be inconsistent during the allocation cutover. Specifically, default allocations may face decreased priority. | * Job priority may be inconsistent during the allocation cutover. Specifically, default allocations may face decreased priority. | ||
* Jobs already in the system will be retained. Running jobs will not be stopped. | * Jobs already in the system will be retained. Running jobs will not be stopped. Waiting jobs may be held. | ||
* Waiting jobs attributed to an allocation which has been moved or not renewed may not schedule after the cutover. Advice on how to detect and handle such jobs will be forthcoming. | * Waiting jobs attributed to an allocation which has been moved or not renewed may not schedule after the cutover. Advice on how to detect and handle such jobs will be forthcoming. | ||