FAS Research Computing - holylabs inaccessible - cluster paused – 사건 세부 정보

일부 시스템에서 성능 저하가 발생했습니다

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.

holylabs inaccessible - cluster paused

해결됨
정상
시작 거의 3년 전지속됨 약 22시간

영향받음

Cannon Cluster

정상 ~에서 6:00 PM ~ 4:02 PM

SLURM Scheduler - Cannon

정상 ~에서 6:00 PM ~ 4:02 PM

Cannon Compute Cluster (Holyoke)

정상 ~에서 6:00 PM ~ 4:02 PM

Boston Compute Nodes

정상 ~에서 6:00 PM ~ 4:02 PM

GPU nodes (Holyoke)

정상 ~에서 6:00 PM ~ 4:02 PM

OpenOnDemand/OOD

정상 ~에서 6:00 PM ~ 4:02 PM

업데이트
  • 해결됨
    해결됨

    We have reverted the routing systems involved in causing this issue to their previous version/state. We will continue to investigate why this issue occurred and what will allow us to upgrade these systems at a later date.

  • 조사 중
    조사 중

    The issue with holylabs (and potentially other lustre filesystems) has recurred. This may have effects on jobs and any process using this and potentially other lustre filesystems.

    No ETA at this time.

  • 해결됨
    해결됨

    We have restored access to holylabs and the cluster/jobs are no longer paused.

    We have identified a root cause which we will be working to remediate to prevent this issue in future.

  • 확인됨
    확인됨

    The scheduler and all jobs have been paused in order to reduce the load on holylabs.

    We are continuing to work on a fix for this incident.

  • 조사 중
    조사 중

    The holylabs filesystem is currently down due to high load.

    OOD, software, and modules are all functional but if your workflow uses holylabs for storage, scripts, or jobs it may hang or fail. Our engineers are investigating this issue further.