FAS Research Computing - Network issues - Cluster degraded – Incident details

All systems operational

Status page for the Harvard FAS Research Computing cluster and other resources.

Cluster Utilization (VPN and FASRC login required): Cannon | FASSE


Please scroll down to see details on any Incidents or maintenance notices.
Monthly maintenance occurs on the first Monday of the month (except holidays).

GETTING HELP
Documentation: https://docs.rc.fas.harvard.edu | Account Portal https://portal.rc.fas.harvard.edu
Email: rchelp@rc.fas.harvard.edu | Support Hours

The colors shown in the bars below were chosen to increase visibility for color-blind visitors.
For higher contrast, switch to light mode at the bottom of this page if the background is dark and colors are muted.

Network issues - Cluster degraded

Resolved
Major outage
Started 4 months agoLasted 5 days

Affected

Cannon Cluster

Degraded performance from 1:34 PM to 8:41 PM

SLURM Scheduler - Cannon

Degraded performance from 1:34 PM to 8:41 PM

Cannon Compute Cluster (Holyoke)

Degraded performance from 1:34 PM to 8:41 PM

Boston Compute Nodes

Degraded performance from 1:34 PM to 8:41 PM

GPU nodes (Holyoke)

Degraded performance from 1:34 PM to 8:41 PM

seas_compute

Degraded performance from 1:34 PM to 8:41 PM

Updates
  • Resolved
    UTC
    Resolved

    This incident has been resolved by draining and rebooting any nodes with stuck mounts.

  • Monitoring
    UTC
    Monitoring

    Mounts to Holyoke Isilon (specifically /n/sw) are broken on numerous nodes across the cluster. We have a check rolling out to find these nodes so we can remediate them individually. Until remediated the cluster will be in a degraded state. Running jobs may randomly die or fail as they hit nodes that have stale mounts.

    It will be risky to run jobs for the next hour and then, after that point, the cluster will have a large number of nodes closed waiting for them to drain so we can reboot them and fix the mounts.

    At this time we are unaware of any holy-isilon problems other than the effect this had on cluster nodes/running jobs. We will update should we identify any data storage concerns.

  • Identified
    UTC
    Identified

    Mounts to Holyoke Isilon (specifically /n/sw) are broken on numerous nodes across the cluster. We have a check rolling out to find these nodes so we can remediate them individually. Until remediated the cluster will be in a degraded state. Running jobs may randomly die or fail as they hit nodes that have stale mounts.

    It will be risky to run jobs for the next hour and then, after that point, the cluster will have a large number of nodes closed waiting for them to drain so we can reboot them and fix the mounts.

  • Investigating
    UTC
    Investigating

    A network issue affecting storage critical to the cluster is It's causing instability. The cluster is currently in a degraded state as a result. We are looking into the problem. Updates to follow..

For issues not shown here, please contact FASRC via
https://portal.rc.fas.harvard.edu or email rchelp@rc.fas.harvard.edu