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
- 완료됨 · 9월 21, 2022 · 21:00UTC
Maintenance has completed successfully
- 진행 중 · 9월 21, 2022 · 13:00UTC
Maintenance is now in progress
- 계획됨 · 9월 21, 2022 · 13: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.

