This is a reminder that our next maintenance is scheduled for Monday, December 4, 8 am–12 pm ET. This will be a full shutdown for the HBSGrid compute cluster, MariaDB, and Globus data transfer nodes, for which ALL jobs and sessions will be terminated. Please plan appropriately.

During the maintenance window:

• • You will not be able to log in to the HBSGrid via terminal or NoMachine.
• • You will not be able to log in to the MariaDB database server.
• • Globus transfers will be temporarily halted.
• • All interactive and batch jobs, as well as database sessions, will be terminated.

What work is being performed and why?

• • We will apply security patches to all nodes in the cluster, to the MariaDB server, and to the Globus data transfer nodes. These changes ensure the safety and stability of our environment.
• • A storage array volume snapshot will be made for the MariaDB server.

We thank you for your anticipated cooperation as we make improvements to our HBSGrid environment. Our next maintenance will occur on Monday, January 8. If you have any questions/comments, please email us at research@hbs.edu.

Our planned work for December will include security patches and updates of all machines in our environment, requiring system restarts. Accordingly, this will be a full cluster, MariaDB, & Globus shutdown, and all interactive and batch jobs will be killed – please plan appropriately. We will send more details about the maintenance later in the week.

We thank you for your cooperation and if you have any questions/comments, please email us at research@hbs.edu.

Our next maintenance is scheduled for Monday, November 6, 8 am –12 pm ET. Access to login nodes, interactive/NoMachine sessions, and Globus nodes will be affected – please plan accordingly.

During the maintenance window:

• • You will not be able to log in to the HBSGrid via terminal or NoMachine.
• • All interactive jobs and NoMachine sessions (connected & disconnected) will be terminated.
• • Globus transfers will be temporarily halted.

What work is being performed and why?

• • We will apply security patches to all nodes in the cluster. These changes ensure the safety and stability of our environment.

We thank you for your patience and cooperation as we make improvements to the HBSGrid. Our next maintenance will occur on Monday, December 4. If you have any questions/comments, please email us at research@hbs.edu.

This is a reminder that our next maintenance is scheduled for Monday, October 2nd, 8 am–12 pm ET. This will be a full shutdown for the HBSGrid compute cluster, MariaDB, and Globus data transfer nodes, for which ALL jobs and sessions will be terminated. Please plan appropriately.

During the maintenance window:

• • You will not be able to log in to the HBSGrid via terminal or NoMachine.
• • You will not be able to log in to the MariaDB database server.
• • Globus transfers will be temporarily halted.
• • All interactive and batch jobs, as well as database sessions, will be terminated.

What work is being performed and why?

• • We will apply security patches to all nodes in the cluster, to the MariaDB server, and to the Globus data transfer nodes. These changes ensure the safety and stability of our environment.
• • A storage array volume snapshot will be made for the MariaDB server.

We thank you for your anticipated cooperation as we make improvements to our HBSGrid environment. Our next maintenance will occur on Monday, September 4th. If you have any questions/comments, please email us at research@hbs.edu.

Our planned work for October will include security patches and updates of all machines in our environment, requiring system restarts. Accordingly, this will be a full cluster, MariaDB, & Globus shutdown, and all interactive and batch jobs will be killed – please plan appropriately. We will send more details about the maintenance next week.

We thank you for your cooperation and if you have any questions/comments, please email us at research@hbs.edu.

Our next maintenance is scheduled for Monday, September 11, 8 am –12 pm ET. Access to login nodes, interactive/NoMachine sessions, and Globus nodes will be affected – please plan accordingly.

During the maintenance window:

• • You will not be able to log in to the HBSGrid via terminal or NoMachine.
• • All interactive jobs and NoMachine sessions (connected & disconnected) will be terminated.
• • Globus transfers will be temporarily halted.

What work is being performed and why?

• • We will apply security patches to all nodes in the cluster. These changes ensure the safety and stability of our environment.
• • We will release module files for updated software titles. Users will be able to access these new versions via the command line, and they will be incorporated into the Grid 3.0 user interface in an upcoming release:
  • Stata 18
  • Stat/Transfer 16
  • MATLAB 2023a
  • Python 3.9.7
  • Mathematica 13.2
  • Gurobi 10.0.1
  • DBeaver 7.3.7

We thank you for your patience and cooperation as we make improvements to the HBSGrid. Our next maintenance will occur on Monday, October 2. If you have any questions/comments, please email us at research@hbs.edu.

This is a reminder that our next maintenance is scheduled for Monday, August 7th, 8 am–12 pm ET. This will be a full shutdown for the HBSGrid compute cluster, MariaDB, and Globus data transfer nodes, for which ALL jobs and sessions will be terminated. Please plan appropriately.

During the maintenance window:

• You will not be able to log in to the HBSGrid via terminal or NoMachine.
• You will not be able to log in to the MariaDB database server.
• Globus transfers will be temporarily halted.
• All interactive and batch jobs, as well as database sessions, will be terminated.

What work is being performed and why?

• • We will apply security patches to all nodes in the cluster, to the MariaDB server, and to the Globus data transfer nodes. These changes ensure the safety and stability of our environment.
• • A storage array volume snapshot will be made for the MariaDB server.
• • We will patch a misconfiguration that allowed certain programs to run on the login nodes.

We thank you for your anticipated cooperation as we make improvements to our HBSGrid environment. Our next maintenance will occur on Monday, September 4th. If you have any questions/comments, please email us at research@hbs.edu.

Our planned work for August will include security patches and updates of all machines in our environment, requiring system restarts. Accordingly, this will be a full cluster, MariaDB, & Globus shutdown, and all interactive and batch jobs will be killed – please plan appropriately. We will send more details about the maintenance next week.

We thank you for your cooperation and if you have any questions/comments, please email us at research@hbs.edu.

Our next maintenance is scheduled for Monday, July 10th, 8 am –12 pm ET. Access to login nodes, interactive/NoMachine sessions, and Globus nodes will be affected – please plan accordingly.

During the maintenance window:

• • You will not be able to log in to the HBSGrid via terminal or NoMachine.
• • All interactive jobs and NoMachine sessions (connected & disconnected) will be terminated.
• • Globus transfers will be temporarily halted.

What work is being performed and why?

• • We will apply security patches to all nodes in the cluster. These changes ensure the safety and stability of our environment.
• • We will update Globus with a patch for the connector to Google Storage.
• • We will add Lmod module files to central installation. This will enable users to access new applications before our upcoming Grid 3.0 release.

We thank you for your patience and cooperation as we make improvements to the HBSGrid. Our next maintenance will occur on Monday, August 7th. If you have any questions/comments, please email us at research@hbs.edu.

This is a reminder that our next maintenance is scheduled for Monday, June 5th, 8 am–12 pm ET. This will be a full shutdown for the HBSGrid compute cluster, MariaDB, and Globus data transfer nodes, for which ALL jobs and sessions will be terminated. Please plan appropriately.

During the maintenance window:

• You will not be able to log in to the HBSGrid via terminal or NoMachine.
• You will not be able to log in to the MariaDB database server.
• Globus transfers will be temporarily halted.
• All interactive and batch jobs, as well as database sessions, will be terminated.

We are making two significant changes that will affect how you work. Please continue to read…

• • The first phase is to retire out-of-warranty hardware – a total of 7 compute nodes (~ 200 cores), most of which were not in production. Combined with the second phase, the net effect for the main queues will be a small increase in capacity.
• • The second phase is to reconfigure the queues to consolidate and prioritize the compute into a larger pool for general use. To accomplish this, we are removing the mini, micro, test, and validation queues. The main queues (short_int, long_int, gpu_int, sas_interactive, short, long, gpu, sas) will remain unaffected.

To ensure your work continues without delay, it is imperative that, moving forward, you right-size your job resource requests: ensure that the cores and RAM you request match what the work requires. Please see our helpful guide on Choosing Resources. As a shared responsibility (for security and access) to yourself and your colleagues, we strongly encourage you to take the time to review your past resource requests and adjust these amounts when starting new jobs. Failure to do so will mean delays or failures in starting applications for yourself and others, and not being able to use particular resources; ultimately resulting in delays performing one's research.

What work is being performed and why?

• • We will apply security patches to all nodes in the cluster, to the MariaDB server, and to the Globus data transfer nodes. These changes ensure the safety and stability of our environment.
• • A storage array volume snapshot will be made for the MariaDB server.
• • We will remove 7 out-of-warranty nodes from the cluster (nod3,4,5,7,8,10,11).
• • We will shift nod25 into the main compute pool.
• • We will remove the test, validation, mini, micro queues.
• • We will patch a misconfiguration that allowed certain programs to run on the login nodes.

We thank you for your anticipated cooperation as we make improvements to our HBSGrid environment. Our next maintenance will occur on Monday, July 10th. If you have any questions/comments, please email us at research@hbs.edu.

Our planned work for June will include security patches and updates of all machines in our environment, requiring system restarts. Accordingly, this will be a full cluster, MariaDB, & Globus shutdown, and all interactive and batch jobs will be killed – please plan appropriately. We will send more details about the maintenance next week.

We thank you for your cooperation and if you have any questions/comments, please email us at research@hbs.edu.

Our next maintenance is scheduled for Monday, May 1st, 8a – 12p. Access to login nodes, interactive/NoMachine sessions, and Globus nodes will be affected – please plan accordingly.

During the maintenance window:

• • You will not be able to log in to the HBSGrid via terminal or NoMachine.
• • All interactive jobs and NoMachine sessions (connected & disconnected) will be terminated.
• • Globus transfers will be temporarily halted.

What work is being performed and why?

• • We will apply security patches to all nodes in the cluster. These changes ensure the safety and stability of our environment.
• • A storage array volume snapshot will be made for the MariaDB server.
• • We will change the cluster configuration so that GPU interactive sessions run in the gpu_int queue only. This will enable us to more closely monitor any problems with PENDing interactive sessions across the cluster.
• • We will change the MATLAB default version to 2022b from 2021b. This update was overlooked during the recent Grid3 update. Please see below if you wish to continue to use 2021b.
• • We will fix a bug that would permit jobs with small, specific resource requests to bypass the scheduler. This fix enables easier troubleshooting and full transparency for resources used on the cluster.
• • We will add a warning message to terminal sessions that are allocated on the login nodes and not the compute nodes. This should help make users aware not to run CPU- or RAM-intensive work on the login nodes, ensuring a better user experience for everyone.

Please note the following important changes:

• • After the maintenance, MATLAB 2022b will be the default version of MATLAB for the current Grid3 release (2022.11). If you wish to remain on 2021b, please select the 2022.01 environment when using the MATLAB launcher (GUI) or execute module load rcs/rcs_2022.01 before starting MATLAB sessions via the terminal.
• • Starting Monday, all GPU interactive sessions should be sent to the gpu_int queue instead of gpu. If you are using the Grid3 UI in NoMachine, you do not need to do anything. If starting interactive jobs via the terminal, use -q gpu_int as the queue option – your interactive job will not be accepted if submitted with -q gpu.

We thank you for your patience and cooperation as we make improvements to the HBSGrid. Our next maintenance will occur on Monday, June 5th. If you have any questions/comments, please email us at research@hbs.edu.