SLURM Scheduler - Cannon - 运行正常
SLURM Scheduler - Cannon
Cannon Compute Cluster (Holyoke) - 运行正常
Cannon Compute Cluster (Holyoke)
Boston Compute Nodes - 运行正常
Boston Compute Nodes
GPU nodes (Holyoke) - 运行正常
GPU nodes (Holyoke)
seas_compute - 运行正常
seas_compute
SLURM Scheduler - FASSE - 运行正常
SLURM Scheduler - FASSE
FASSE Compute Cluster (Holyoke) - 运行正常
FASSE Compute Cluster (Holyoke)
Kempner Cluster CPU - 运行正常
Kempner Cluster CPU
Kempner Cluster GPU - 运行正常
Kempner Cluster GPU
FASSE login nodes - 运行正常
FASSE login nodes
Cannon Open OnDemand - 运行正常
Cannon Open OnDemand
FASSE Open OnDemand - 运行正常
FASSE Open OnDemand
Netscratch (Global Scratch) - 运行正常
Netscratch (Global Scratch)
Home Directory Storage - Boston - 运行正常
Home Directory Storage - Boston
Tape - (Tier 3) - 运行正常
Tape - (Tier 3)
Holylabs - 运行正常
Holylabs
Isilon Storage Holyoke (Tier 1) - 运行正常
Isilon Storage Holyoke (Tier 1)
Holystore01 (Tier 0) - 运行正常
Holystore01 (Tier 0)
HolyLFS04 (Tier 0) - 运行正常
HolyLFS04 (Tier 0)
HolyLFS05 (Tier 0) - 运行正常
HolyLFS05 (Tier 0)
HolyLFS06 (Tier 0) - 运行正常
HolyLFS06 (Tier 0)
Holyoke Tier 2 NFS - 运行正常
Holyoke Tier 2 NFS
Holyoke Specialty Storage - 运行正常
Holyoke Specialty Storage
holECS - 运行正常
holECS
Isilon Storage Boston (Tier 1) - 运行正常
Isilon Storage Boston (Tier 1)
BosLFS02 (Tier 0) - 运行正常
BosLFS02 (Tier 0)
Boston Tier 2 NFS - 运行正常
Boston Tier 2 NFS
CEPH Storage Boston (Tier 2) - 运行正常
CEPH Storage Boston (Tier 2)
Boston Specialty Storage - 运行正常
Boston Specialty Storage
bosECS - 运行正常
bosECS
Samba Cluster - 运行正常
Samba Cluster
Globus Data Transfer - 运行正常
Globus Data Transfer
历史记录
查看当前状态11月 2022
10月 2022
9月 2022
- 已完成 · 九月 21, 2022 在 下午 9:00UTC
Maintenance has completed successfully
- 进行中 · 九月 21, 2022 在 下午 1:00UTC
Maintenance is now in progress
- 已计划 · 九月 21, 2022 在 下午 1:00UTC
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.
- 已解决 · 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.
- 更新 · UTC
Difficulty obtaining replacement mainboards has this issue stalled. More information when we have it.
- 更新 · 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
- 更新 · 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.
- 已确认问题 · UTC
Please note that this issue also affects the remoteviz partition.
Updates as we have them.
- 调查中 · 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.

