SLURM Scheduler - Cannon - Operational
SLURM Scheduler - Cannon
Cannon Compute Cluster (Holyoke) - Operational
Cannon Compute Cluster (Holyoke)
Boston Compute Nodes - Operational
Boston Compute Nodes
GPU nodes (Holyoke) - Operational
GPU nodes (Holyoke)
seas_compute - Operational
seas_compute
SLURM Scheduler - FASSE - Operational
SLURM Scheduler - FASSE
FASSE Compute Cluster (Holyoke) - Operational
FASSE Compute Cluster (Holyoke)
Kempner Cluster CPU - Operational
Kempner Cluster CPU
Kempner Cluster GPU - Operational
Kempner Cluster GPU
FASSE login nodes - Operational
FASSE login nodes
Cannon Open OnDemand - Operational
Cannon Open OnDemand
FASSE Open OnDemand - Operational
FASSE Open OnDemand
Netscratch (Global Scratch) - Operational
Netscratch (Global Scratch)
Home Directory Storage - Boston - Operational
Home Directory Storage - Boston
Tape - (Tier 3) - Operational
Tape - (Tier 3)
Holylabs - Operational
Holylabs
Isilon Storage Holyoke (Tier 1) - Operational
Isilon Storage Holyoke (Tier 1)
Holystore01 (Tier 0) - Operational
Holystore01 (Tier 0)
HolyLFS04 (Tier 0) - Operational
HolyLFS04 (Tier 0)
HolyLFS05 (Tier 0) - Operational
HolyLFS05 (Tier 0)
HolyLFS06 (Tier 0) - Operational
HolyLFS06 (Tier 0)
Holyoke Tier 2 NFS - Operational
Holyoke Tier 2 NFS
Holyoke Specialty Storage - Operational
Holyoke Specialty Storage
holECS - Operational
holECS
Isilon Storage Boston (Tier 1) - Operational
Isilon Storage Boston (Tier 1)
BosLFS02 (Tier 0) - Operational
BosLFS02 (Tier 0)
Boston Tier 2 NFS - Operational
Boston Tier 2 NFS
CEPH Storage Boston (Tier 2) - Operational
CEPH Storage Boston (Tier 2)
Boston Specialty Storage - Operational
Boston Specialty Storage
bosECS - Operational
bosECS
Samba Cluster - Operational
Samba Cluster
Globus Data Transfer - Major outage
Globus Data Transfer
Notice history
View current statusNov 2022
Oct 2022
Sep 2022
- Completed · September 21, 2022 at 9:00 PMUTC
Maintenance has completed successfully
- In progress · September 21, 2022 at 1:00 PMUTC
Maintenance is now in progress
- Planned · September 21, 2022 at 1:00 PMUTC
Our service partner New England Research Cloud (NERC) has a planned maintenance event on Wednesday 9/21/22 from 9am to 5pm.
If you are a NERC user, please see: https://nerc.instatus.com/cl6qt8sbr2993aemv5algl4ih Updates will be shown on their status page.
You can also subscribe to their status page by following that link and clicking Get Updates and choosing your notification method.
- Resolved · UTC
This issue has become one of supply and availability. As such, we are changing this issue to Maintenance as there is nothing further we can do until the vendor replaces the hardware. Please continue to use other GPU resources. We will notify the community once we have new hardware to replenish the gpu_test queue.
Please see Running Jobs for other available resources.
- Update · UTC
Difficulty obtaining replacement mainboards has this issue stalled. More information when we have it.
- Update · UTC
Correction to first part of previous update:
Currently only 2 of the nodes in gpu_test are working and the single remoteviz node is down. These will require help from the vendor to revive. We are also investigating with them the root cause for multiple node failures. No ETA
- Update · UTC
Currently only 2 of the nodes in gpu_test are working and the single remoteviz node is down. These will require help from the vendor to revive. We are also investigating with them the root cause for multiple node failures. No ETA
As a result of this, we are pre-emptively modifying the QoS for gpu_test now. We had planned to make a change on Thursday after announcing it in tomorrow's maintenance email, but this forces our hand.
QoS changes for gpu_test effective now: Limited to 1 job per user. That job is limited to a maximum 16 cores and 90GB memory.
See Running Jobs for a list of available partitions, including the gpu partition.
- Identified · UTC
Please note that this issue also affects the remoteviz partition.
Updates as we have them.
- Investigating · UTC
Several hosts in the gpu_test queue have become unresponsive and will require a physical visit to reset. Staff are en route to the data center.
On a related note, please do not use gputest as a workaround for the regular gpuqueues.
This is unfair to other users and ties up the gpu_test partition. This partition is not for general job use.We will be addressing this issue later this week by reducing the number of jobs allowed per user. This will be noted in tomorrow's maintenance email and then implemented Thursday.

