SLURM Scheduler - Cannon - I drift
SLURM Scheduler - Cannon
Cannon Compute Cluster (Holyoke) - I drift
Cannon Compute Cluster (Holyoke)
Boston Compute Nodes - I drift
Boston Compute Nodes
GPU nodes (Holyoke) - I drift
GPU nodes (Holyoke)
seas_compute - I drift
seas_compute
SLURM Scheduler - FASSE - I drift
SLURM Scheduler - FASSE
FASSE Compute Cluster (Holyoke) - I drift
FASSE Compute Cluster (Holyoke)
Kempner Cluster CPU - I drift
Kempner Cluster CPU
Kempner Cluster GPU - I drift
Kempner Cluster GPU
FASSE login nodes - I drift
FASSE login nodes
Cannon Open OnDemand - I drift
Cannon Open OnDemand
FASSE Open OnDemand - I drift
FASSE Open OnDemand
Netscratch (Global Scratch) - I drift
Netscratch (Global Scratch)
Home Directory Storage - Boston - I drift
Home Directory Storage - Boston
Tape - (Tier 3) - I drift
Tape - (Tier 3)
Holylabs - I drift
Holylabs
Isilon Storage Holyoke (Tier 1) - I drift
Isilon Storage Holyoke (Tier 1)
Holystore01 (Tier 0) - I drift
Holystore01 (Tier 0)
HolyLFS04 (Tier 0) - I drift
HolyLFS04 (Tier 0)
HolyLFS05 (Tier 0) - I drift
HolyLFS05 (Tier 0)
HolyLFS06 (Tier 0) - I drift
HolyLFS06 (Tier 0)
Holyoke Tier 2 NFS - I drift
Holyoke Tier 2 NFS
Holyoke Specialty Storage - I drift
Holyoke Specialty Storage
holECS - I drift
holECS
Isilon Storage Boston (Tier 1) - I drift
Isilon Storage Boston (Tier 1)
BosLFS02 (Tier 0) - Stort avbrott
BosLFS02 (Tier 0)
Boston Tier 2 NFS - I drift
Boston Tier 2 NFS
CEPH Storage Boston (Tier 2) - I drift
CEPH Storage Boston (Tier 2)
Boston Specialty Storage - I drift
Boston Specialty Storage
bosECS - I drift
bosECS
Samba Cluster - I drift
Samba Cluster
Globus Data Transfer - I drift
Globus Data Transfer
Meddelandehistorik
Visa aktuell statusjuli 2023
juni 2023
- Planerat · juni 20, 2023 kl 11:00UTC
WHAT
Emergency Cannon cluster scheduler maintenance Tuesday June 20th from 7am - 11am (actual end time estimated). Running jobs will be paused during maintenance.Note: FASSE is unaffected by this.
WHY
As most of you know, there are on-going issues with the Cannon scheduler after the downtime and OS upgrades. This behavior did not show up in our earlier testing and only manifested once we were under load from user jobs again.After investigation we found that the scheduler is oscillating between two states every hour. During even hours the scheduler would enter a high thread state where all the traffic would pile up, causing any queries to either take a long time or time out. During odd hours the scheduler would enter a low thread state and operate normally. During periods where the scheduler is responding, jobs can be submitted and should then run normally.
Unfortunately the root cause is still not known, and we are working closely with the vendor, SchedMD, to find a solution to return the cluster to stability. The version of slurm that we are running is 22.05.7, which while very stable — we have been running on it for the past 5 months with no problems — appears to be having issues at scale on Rocky 8.
There is a newer version of the scheduler available, 23.02.3. This new version has a host of improvements. While the specific issue described above is not listed as one of the items fixed in this version, we anticipate that the upgrade may fix this issue owing to the various code improvements contained therein.
Barring any solutions found over the long weekend, we intend to hold an emergency maintenance period on Tuesday June 20th starting at 7am. Running jobs will be paused. We will return Cannon to service as soon as we've completed work. Status of this maintenance will be tracked here on our status page.
We thank you for your patience and understanding. Our team is hard at work answering your tickets and making sure that the cluster is back to full health. Also as a reminder that we hold additional Office Hours each week in June. See: https://www.rc.fas.harvard.edu/training/office-hours/
FAS Research Computing
https://www.rc.fas.harvard.edu/
https://docs.rc.fas.harvard.edu/
https://status.rc.fas.harvard.edu/ - Slutfört · juni 20, 2023 kl 01:16UTC
CANCELLED
Emergency maintenance has has been cancelled. A solution to the scheduler issue has been found and Slurm is once again operating normally.
We thank you for your patience and understanding.

