FAS Research Computing - Cannon cluster down – Incident details

Experiencing partially degraded performance

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.

Cannon cluster down

Identified
Major outage
Started about 11 hours ago

Affected

Cannon Cluster

Major outage from 8:21 PM to 9:13 PM, Degraded performance from 9:13 PM to 12:00 AM

SLURM Scheduler - Cannon

Major outage from 8:21 PM to 9:13 PM, Degraded performance from 9:13 PM to 12:00 AM

Cannon Compute Cluster (Holyoke)

Major outage from 8:21 PM to 9:13 PM, Degraded performance from 9:13 PM to 12:00 AM

Boston Compute Nodes

Major outage from 8:21 PM to 9:13 PM, Degraded performance from 9:13 PM to 12:00 AM

GPU nodes (Holyoke)

Major outage from 8:21 PM to 9:13 PM, Degraded performance from 9:13 PM to 12:00 AM

seas_compute

Major outage from 8:21 PM to 9:13 PM, Degraded performance from 9:13 PM to 12:00 AM

Updates
  • Identified
    Identified

    To temporarily stabilize the situation, we have reduced the maximum query time for sacct and other Slurm commands to be 1 day. We have filed a ticket with SchedMD to further analyze the issue.

    The cluster is back up and the scheduler is accepting new jobs.

    We will continue to monitor for emergencies over the weekend, and resume in-depth troubleshooting on Monday.

  • Investigating
    Investigating

    The Slurm scheduler is experiencing an error which is impacting jobs. The Cannon cluster will be inaccessible while we troubleshoot.

    We are currently investigating this incident.