[Lilab] Fwd: [HPCC] Maintenance Shutdown Confirmation

[Wei Vivian Li]

FYI. Please mark this maintenance on your calendars and plan accordingly.


---------- Forwarded message ---------
From: <no-reply at hpcc.ucr.edu>
Date: Tue, Jul 18, 2023 at 9:04 PM
Subject: [HPCC] Maintenance Shutdown Confirmation
To: <no-reply at hpcc.ucr.edu>


Hello HPCC users,

HPCC staff will be performing a maintenance shutdown on *Friday, August 4,
2023* at *noon*, and will last into *Saturday afternoon*. This shutdown
will focus on finalizing electrical work that began during the May
shutdown, which is necessary for supporting the incoming NSF-funded nodes,
as well as activating all available bigdata storage space. In addition,
routine updates to system software will be performed.

During the shutdown, all of our online services hosted from the Genomics
Building will be unavailable. This includes, but is not limited to: SSH,
Slurm, Rstudio Server, JupyterHub, web file access, and email support. Our
primary method of communication during the shutdown will be our Slack
channel:

https://ucr-hpcc.slack.com/

If your compute job duration extends into the maintenance window, you will
receive a "ReqNodeNotAvail" error, and your job will not start. It is
recommended to reduce the duration of your job such that it will finish
before the aformentioned time. *Unlike the previous shutdown, we are
expecting to start from a fresh Slurm installation. What this means is that
pending jobs will not automatically start after the shutdown; you must
manually resubmit your pending jobs.*

We understand that interruptions like this are disruptive to your research
and teaching, and for that we apologize. However, these maintenance
shutdowns are necessary for the reliability and performance of our cluster
services. Thank you for your understanding.

Sincerely,

Austin Leong
UCR High Performance Computing Center
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ucr.edu/pipermail/lilab/attachments/20230718/914bb3b3/attachment.html>