FAS Research Computing - Histórico de avisos

Experimentando Desempenho Parcialmente Degradado

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.

Desempenho degradado

SLURM Scheduler - Cannon - Desempenho degradado

Cannon Compute Cluster (Holyoke) - Desempenho degradado

Boston Compute Nodes - Desempenho degradado

GPU nodes (Holyoke) - Desempenho degradado

seas_compute - Desempenho degradado

Operacional

SLURM Scheduler - FASSE - Operacional

FASSE Compute Cluster (Holyoke) - Operacional

Operacional

Kempner Cluster CPU - Operacional

Kempner Cluster GPU - Operacional

Operacional

FASSE login nodes - Operacional

Operacional

Cannon Open OnDemand/VDI - Operacional

FASSE Open OnDemand/VDI - Operacional

Operacional

Netscratch (Global Scratch) - Operacional

Home Directory Storage - Boston - Operacional

Tape - (Tier 3) - Operacional

Holylabs - Operacional

Isilon Storage Holyoke (Tier 1) - Operacional

Holystore01 (Tier 0) - Operacional

HolyLFS04 (Tier 0) - Operacional

HolyLFS05 (Tier 0) - Operacional

HolyLFS06 (Tier 0) - Operacional

Holyoke Tier 2 NFS (new) - Operacional

Holyoke Specialty Storage - Operacional

holECS - Operacional

Isilon Storage Boston (Tier 1) - Operacional

BosLFS02 (Tier 0) - Operacional

Boston Tier 2 NFS (new) - Operacional

CEPH Storage Boston (Tier 2) - Operacional

Boston Specialty Storage - Operacional

bosECS - Operacional

Samba Cluster - Operacional

Globus Data Transfer - Operacional

Histórico de avisos

mar 2026

Scheduler is degraded
  • Resolvido
    Resolvido

    This incident has been resolved. The scheduler is running normally.

  • Investigando
    Investigando

    The scheduler is in a degraded state due to thrashing
    We are actively working to resolve this problem.

Network issues - Cluster degraded
  • Resolvido
    Resolvido

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

  • Monitorização
    Monitorização

    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.

  • Identificado
    Identificado

    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.

  • Investigando
    Investigando

    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..

fev 2026

Tape outage
  • Resolvido
    Resolvido

    This incident has been resolved. Normal tape operations are restored.

  • Monitorização
    Monitorização

    The tape library outage is further extended to Wednesday March 4th at 9am awaiting a hardware replacement part due today. Data can still be uploaded to lab collections via Globus, but be mindful of the 10 TB buffer file limit. The outage affects storage and recall from tape.

  • Identificado
    Identificado

    NESE Tape Service is still working with IBM technical support at restoring the inventory. The expected downtime is extended until Tuesday March 3rd, 9am.
    Apologies for the inconvenvenience.

  • Investigando
    Investigando

    NESE Tape service will be down or operating with degraded service (no store and recall) Friday from 12 Noon EST until as late as Monday, 2 March at 9 AM.

    SUMMARY OF ISSUE:

    NESE Tape service is currently not able to store or recall files to and from tape due to vendor firmware issues in the IBM TS4500 tape library. The issue is related to the library robotics and cartridge database and we do NOT expect any data loss from this issue.

    The issue is apparently due to an issue with the inventory database related to a recent firmware update. This database can be scrubbed and reconstructed by the library, which will scan the bar code labels on all the cartridges to rebuild the inventory. Association of files in Globus to tapes is handled separately from the tape library and is not affected by the firmware update.

NESE tape maintenance Feb 19th 2026
  • Concluído
    fevereiro 19, 2026 em 22:00
    Concluído
    fevereiro 19, 2026 em 22:00
    Maintenance has completed successfully
  • Em curso
    fevereiro 19, 2026 em 13:00
    Em curso
    fevereiro 19, 2026 em 13:00
    Maintenance is now in progress
  • Ainda não começou
    fevereiro 19, 2026 em 13:00
    Ainda não começou
    fevereiro 19, 2026 em 13:00

    From our partners at NESE. Details follow:

    We are installing four new tape frames, which will bring the tape system raw storage capacity to 253 petabytes.

    Service Affected: NESE Tape Service

    Maintenance Window: 8:00 AM - 5:00 PM (EST)

    • The tape service will be unavailable.

    • All upgrade activities are expected to be completed on the same day.

    NOTES:

    • Monitor the MGHPCC Slack #nese channel for status updates and announcements

    • Monitor https://nese.instatus.com/ for real-time updates on progress

    Subscribe to https://nese.instatus.com/subscribe/email for updates and announcements

jan 2026

FASRC monthly maintenance Monday January 12th, 2026 9am-1pm
  • Concluído
    janeiro 12, 2026 em 18:00
    Concluído
    janeiro 12, 2026 em 18:00
    Maintenance has completed successfully
  • Em curso
    janeiro 12, 2026 em 14:00
    Em curso
    janeiro 12, 2026 em 14:00
    Maintenance is now in progress
  • Ainda não começou
    janeiro 12, 2026 em 14:00
    Ainda não começou
    janeiro 12, 2026 em 14:00

    Monthly maintenance will take place on January 12th, 2026. Our maintenance tasks should be completed between 9am-1pm.

    NOTICES:

    • Changes to SEAS partitions, please see tasks below.

    • Changes to job age priority weighting, please see tasks below.

    • Status Page: You can subscribe to our status to receive notifications of maintenance, incidents, and their resolution at https://status.rc.fas.harvard.edu/ (click Get Updates for options).

    • We'd love to hear success stories about your or your lab's use of FASRC. Submit your story here.

    MAINTENANCE TASKS

    Cannon cluster will be paused during this maintenance?: YES
    FASSE cluster will be paused during this maintenance?:YES

    • Slurm upgrade to 25.11.1

      • Audience: All cluster users (Cannon and FASSE)

      • Impact: Jobs will be paused during maintenance

    • In conjunction with SEAS we will modify seas_gpu and seas_compute time limits 

      • Audience: SEAS users

      • Impact:
        seas_gpu: will be set to 2 days maximum
        seas_compute: will be set to 3 days maximum

        Existing pending jobs longer than these limits will be set to 2 day and 3 day run times depending on partition.

    • Job Age Priority Weight Change

      • Audience: Cluster users

      • Impact: We will be adjusting the weight applied to the priority earned by jobs by virtue of their age. Currently job priority is made up of two factors, Fairshare and Job Age. The Job Age factor is currently set such that jobs gain priority over 3 days with a maximum priority equivalent to jobs with Fairshare of 0.5. This keeps low fairshare jobs from languishing at the bottom of the queue. With the current settings though, users with low fairshare can gain significant advantage over users with higher relative fairshare. To remedy this we will be adjusting the Job Age weight to cap out at an equivalent Fairshare of 0.1. This will still allow jobs with 0 fairshare to gain priority and thus not languish while letting fairshare govern a wider range of higher priority jobs.

    • Login node reboots

      • Audience; All login node users

      • Impact: Login nodes will reboot during the maintenance window

    • Open OnDemand (OOD) node reboots

      • Audienc:; All OOD users

      • Impact: OOD nodes will reboot during the maintenance window

    • Netscratch retention will run

      • Audience: All cluster netscratch users

      • Impact: Files older than 90 days will be removed. Please note that retention cleanup can and does run at any time, not just during the maintenance window.

    Thank you,
    FAS Research Computing
    https://docs.rc.fas.harvard.edu/
    https://www.rc.fas.harvard.edu/

jan 2026 para mar 2026

Seguinte