cc_staff
158
edits
RAC transition FAQ: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
<!--T:1--> | <!--T:1--> | ||
Allocations from the | Allocations from the 2020 Resource Allocation Competition come into effect on April 1, 2020. | ||
Here are some notes on how we expect the transition from | Here are some notes on how we expect the transition from 2019 to 2020 allocations to go. | ||
=== Storage === <!--T:2--> | === Storage === <!--T:2--> | ||
* There will be 30 days of overlap between 2019 and 2020 storage allocations, starting on April 1, 2020. | * There will be 30 days of overlap between 2019 and 2020 storage allocations, starting on April 1, 2020. | ||
* On a given system the largest of the two quotas ( | * On a given system the largest of the two quotas (2019, 2020) will be adopted during the transition period. | ||
* If an allocation has moved from one site to another, users are expected to transfer the data by themselves (via globus, scp, rsync, ''etc.''; see [[Transferring data]]). For large amounts of data (''e.g.'', 200TB or more) please [[Technical support|contact support]] for advice or assistance to manage the transfer. | * If an allocation has moved from one site to another, users are expected to transfer the data by themselves (via globus, scp, rsync, ''etc.''; see [[Transferring data]]). For large amounts of data (''e.g.'', 200TB or more) please [[Technical support|contact support]] for advice or assistance to manage the transfer. | ||
* Groups with an allocation that has been moved to [[Béluga/en|Béluga]] are encouraged to start migrating their data '''now.''' Béluga storage is already accessible via Globus | * Groups with an allocation that has been moved to [[Béluga/en|Béluga]] are encouraged to start migrating their data '''now.''' Béluga storage is already accessible via Globus | ||
| Line 19: | Line 19: | ||
=== Job scheduling === <!--T:3--> | === Job scheduling === <!--T:3--> | ||
* 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. | * 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 | * We expect to begin replacing 2019 allocations with 2020 allocations on April 1. | ||
* 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. Waiting jobs may be held. | * Jobs already in the system will be retained. Running jobs will not be stopped. Waiting jobs may be held. | ||