RAC transition FAQ: Difference between revisions
Jump to navigation
Jump to search
m (Rdickson moved page RAC 2019 transition FAQ to RAC transition FAQ without leaving a redirect: Part of translatable page "RAC 2019 transition FAQ") |
No edit summary |
||
| Line 11: | Line 11: | ||
* On a given system, the largest of the two quotas (2019, 2020) will be adopted during the transition period. | * 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. | ||
* Contributed storage systems have different dates of activation and decommissioning. For these, we'll be doing the SUM(2019, 2020) for quotas during the 30 days transition period. | * Contributed storage systems have different dates of activation and decommissioning. For these, we'll be doing the SUM(2019, 2020) for quotas during the 30 days transition period. | ||
* For every other PI, we use default quotas. | * For every other PI, we use default quotas. | ||
Revision as of 16:34, 21 February 2020
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 2019 to 2020 allocations to go.
Storage
- 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 (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 contact support for advice or assistance to manage the transfer.
- Contributed storage systems have different dates of activation and decommissioning. For these, we'll be doing the SUM(2019, 2020) for quotas during the 30 days transition period.
- For every other PI, we use default quotas.
- After the transition period, the quotas on the original sites from which data has been migrated will also be set to default. Users are expected to delete data from those original sites if the usage levels are above the new (default) quota. If usage remains above the new quota after the overlap period, staff may choose to delete everything.
- Reasonable requests for extension of the overlap period will be honoured, but such an extension may be impossible or severely constrained if the original cluster is being defunded.
Job scheduling
- The scheduler team is planning to archive and compact the Slurm database on March 31 before implementing the new allocations on April 1. We hope to schedule the archive and compaction during off-peak hours. During this time the database may be unresponsive. Specifically, sacct and sacctmgr may be unresponsive.
- 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.
- 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.