SLURM Scheduler - Cannon - Operativo
SLURM Scheduler - Cannon
Cannon Compute Cluster (Holyoke) - Operativo
Cannon Compute Cluster (Holyoke)
Boston Compute Nodes - Operativo
Boston Compute Nodes
GPU nodes (Holyoke) - Operativo
GPU nodes (Holyoke)
seas_compute - Operativo
seas_compute
SLURM Scheduler - FASSE - Operativo
SLURM Scheduler - FASSE
FASSE Compute Cluster (Holyoke) - Operativo
FASSE Compute Cluster (Holyoke)
Kempner Cluster CPU - Operativo
Kempner Cluster CPU
Kempner Cluster GPU - Operativo
Kempner Cluster GPU
FASSE login nodes - Operativo
FASSE login nodes
Cannon Open OnDemand - Operativo
Cannon Open OnDemand
FASSE Open OnDemand - Operativo
FASSE Open OnDemand
Netscratch (Global Scratch) - Operativo
Netscratch (Global Scratch)
Home Directory Storage - Boston - Operativo
Home Directory Storage - Boston
Tape - (Tier 3) - Operativo
Tape - (Tier 3)
Holylabs - Operativo
Holylabs
Isilon Storage Holyoke (Tier 1) - Operativo
Isilon Storage Holyoke (Tier 1)
Holystore01 (Tier 0) - Operativo
Holystore01 (Tier 0)
HolyLFS04 (Tier 0) - Operativo
HolyLFS04 (Tier 0)
HolyLFS05 (Tier 0) - Operativo
HolyLFS05 (Tier 0)
HolyLFS06 (Tier 0) - Interrupción grave
HolyLFS06 (Tier 0)
Holyoke Tier 2 NFS - Operativo
Holyoke Tier 2 NFS
Holyoke Specialty Storage - Operativo
Holyoke Specialty Storage
holECS - Operativo
holECS
Isilon Storage Boston (Tier 1) - Operativo
Isilon Storage Boston (Tier 1)
BosLFS02 (Tier 0) - Operativo
BosLFS02 (Tier 0)
Boston Tier 2 NFS - Operativo
Boston Tier 2 NFS
CEPH Storage Boston (Tier 2) - Operativo
CEPH Storage Boston (Tier 2)
Boston Specialty Storage - Operativo
Boston Specialty Storage
bosECS - Operativo
bosECS
Samba Cluster - Operativo
Samba Cluster
Globus Data Transfer - Operativo
Globus Data Transfer
Historial de avisos
Ver estado actualfeb 2026
- Completado · febrero 19, 2026 a 22:00UTCMaintenance has completed successfully
- En curso · febrero 19, 2026 a 13:00UTCMaintenance is now in progress
- Planificado · febrero 19, 2026 a 13:00UTC
From our partners at NESE. Details follow:
We are installing four new tape frames, which will bring the tape system raw storage capacity to 253 petabytes.
Service Affected: NESE Tape Service
Maintenance Window: 8:00 AM - 5:00 PM (EST)
The tape service will be unavailable.
All upgrade activities are expected to be completed on the same day.
NOTES:
Monitor the MGHPCC Slack #nese channel for status updates and announcements
Monitor https://nese.instatus.com/ for real-time updates on progress
Subscribe to https://nese.instatus.com/subscribe/email for updates and announcements
ene 2026
- Completado · enero 12, 2026 a 18:00UTCMaintenance has completed successfully
- En curso · enero 12, 2026 a 14:00UTCMaintenance is now in progress
- Planificado · enero 12, 2026 a 14:00UTC
Monthly maintenance will take place on January 12th, 2026. Our maintenance tasks should be completed between 9am-1pm.
NOTICES:
Changes to SEAS partitions, please see tasks below.
Changes to job age priority weighting, please see tasks below.
Status Page: You can subscribe to our status to receive notifications of maintenance, incidents, and their resolution at https://status.rc.fas.harvard.edu/ (click Get Updates for options).
We'd love to hear success stories about your or your lab's use of FASRC. Submit your story here.
MAINTENANCE TASKS
Cannon cluster will be paused during this maintenance?: YES
FASSE cluster will be paused during this maintenance?:YESSlurm upgrade to 25.11.1
Audience: All cluster users (Cannon and FASSE)
Impact: Jobs will be paused during maintenance
In conjunction with SEAS we will modify seas_gpu and seas_compute time limits
Audience: SEAS users
Impact:
seas_gpu: will be set to 2 days maximum
seas_compute: will be set to 3 days maximumExisting pending jobs longer than these limits will be set to 2 day and 3 day run times depending on partition.
Job Age Priority Weight Change
Audience: Cluster users
Impact: We will be adjusting the weight applied to the priority earned by jobs by virtue of their age. Currently job priority is made up of two factors, Fairshare and Job Age. The Job Age factor is currently set such that jobs gain priority over 3 days with a maximum priority equivalent to jobs with Fairshare of 0.5. This keeps low fairshare jobs from languishing at the bottom of the queue. With the current settings though, users with low fairshare can gain significant advantage over users with higher relative fairshare. To remedy this we will be adjusting the Job Age weight to cap out at an equivalent Fairshare of 0.1. This will still allow jobs with 0 fairshare to gain priority and thus not languish while letting fairshare govern a wider range of higher priority jobs.
Login node reboots
Audience; All login node users
Impact: Login nodes will reboot during the maintenance window
Open OnDemand (OOD) node reboots
Audienc:; All OOD users
Impact: OOD nodes will reboot during the maintenance window
Netscratch retention will run
Audience: All cluster netscratch users
Impact: Files older than 90 days will be removed. Please note that retention cleanup can and does run at any time, not just during the maintenance window.
Thank you,
FAS Research Computing
https://docs.rc.fas.harvard.edu/
https://www.rc.fas.harvard.edu/
dic 2025
- Resuelto · UTC
We have found the malformed job which caused the scheduler to wedge and have cancelled it. We will continue to work with SchedMD to prevent future stalls. The scheduler is back in operation. Happy Holidays!
- Actualizar · UTC
We have filed a ticket with SchedMD to diagnose the issue (https://support.schedmd.com/show_bug.cgi?id=24376). All partitions are set to DOWN as we assess the situation
- Investigando · UTC
The slurm scheduler ground to halt at 3pm EST. We are investigating the cause.

