How does this impact you

In practice, most users will not see a difference in their experience on Negishi compared to Data Workbench. You can continue to access the remote desktop by connecting to desktop.negishi.rcac.purdue.edu (instead of desktop.workbench.rcac.purdue.edu). If you use RStudio Server or JupyterHub on Data Workbench, you can continue using them after the transition through the OnDemand front-end at gateway.negishi.rcac.purdue.edu. Please begin referencing Negishi's user-guides after the transition.

Any sessions or computing tasks that are active at the time of transition (Dec. 6) will be terminated.

Soon you will be greeted by automated notification emails stating that an account has been created for you. You will be able to manage access to the Negishi resource just the same as you have always been able to for Data Workbench. This “queue” is needed to manage user access for your group but will not be granted any compute nodes (just as was the case for Data Workbench). For OnDemand users, they should target the new interactive queue in the drop-down menu.

Negishi has its own home directory file system. If you wish to migrate your files from your home directory on Data Workbench, Globus (transfer.rcac.purdue.edu) offers the simplest means to do that (see rcac.purdue.edu/training/globus). Simply target the “Purdue Research Computing – Home Directories” as the source and “Purdue Negishi Cluster” as the destination. Any data stored in Data Depot will continue to be available to you and requires no action.

Please reach out to rcac-help@purdue.edu with any questions you may have.

On Monday, November 27th, RCAC hosted a Data Workbench Service Transition Support Session. The recording is now available!

Globus transfers to/from Data Depot may experience slowdowns as well. The SMB/Windows network drive functionality is not affected.

We appreciate the incident reports we received. RCAC engineers are working with the vendor on diagnosing and troubleshooting the issue.

PurdueIT is replacing our ticketing system, Footprints, with a new product called Team Dynamix (TDX).

Email to rcac-help@purdue.edu will begin to forward to the TDX environment effective Wednesday, July 12, 2023.

You may notice a difference in the format of our replies, and some new text at the bottom of the emails.

With this new system, you can also log into the service portal to see and track any open issues that you have across the entire PurdueIT system. The portal is located at https://service.purdue.edu

We are moving quickly into the new system and there will be a learning curve for Staff as well as partners. We are dedicated to learning and improving our processes as diligently as possible.

Another note for support concerns the week of July 24-28. Several of our staff will be attending an annual conference that week and responses may be slower than normal. We will watch the ticket queue and reply as we are able. Coffee hours will also be canceled for that week

Thanks for being our partner in HPC.

Rosen Center Staff

https://it.purdue.edu/login/

SSH keys will continue to work uninterrupted, and users of ACCESS systems will see no change to their accounts/access. Only BoilerKey-based login to RCAC systems will be affected by this change. There may be interruptions in login via BoilerKey and Purdue Login around the time of transition just before and after midnight.

We will post a more detailed guide on the exact changes and impacts observed to RCAC systems on Tuesday, June 27th. Thank you for your patience during this big transition for Purdue!

Research Computing staff members will monitor the status of all computing and data resources in an effort to ensure continuous availability.

Research Computing staff members will monitor the ticketing system throughout the holiday period and respond to critical issues and problems. Non-critical user issues and questions will be addressed beginning Tuesday, January 3rd, 2023. There will also be no coffee hour consultations during this break.

Scratch file purging (on community clusters with scratch space) will continue as normal during the break, so be sure to archive your files in scratch storage or check for any upcoming purge warning emails during the break. This does not apply to Data Depot or home directories -- only scratch storage.

Have a wonderful break, everyone, and we look forward to great things in the new year!

System engineers are actively engaged with the vendor to troubleshoot and fix the glitch. We appreciate your patience and will provide another update by 6pm.

The clusters will return to full production by Wednesday, March 16th, 2022 at 12:00pm EDT.

Any SLURM jobs which request a walltime which would take them past Tuesday, March 15th, 2022 at 4:00pm EDT will not start and will remain in the queue until after the maintenance is completed. Please note that the downtime for the clusters is longer than the Whole-Floor Data Depot Maintenance (due to extra time required to bring clusters down and back up once the actual Data Depot work is completed).

We will provide an update by 6pm.

The cluster began experiencing issues with the Data Depot filesystem around 5:45pm EST on Friday, February 11th, 2022. Engineers are currently diagnosing the issue and are working to identify a fix. Job scheduling has been paused while this issue is being addressed.

We will provide an update later tonight.

Research Computing staff members will monitor the status of all computing and data resources in an effort to ensure continuous availability.

Research Computing staff members will monitor the ticketing system throughout the holiday period and answer critical user questions. Non-critical user questions will be addressed beginning Monday, January 3rd, 2022. There will also be no coffee hour consultations during this break.

Scratch file purging (on community clusters with scratch space) will continue as normal during the break, so be sure to archive your files in scratch storage or check for any upcoming purge warning email during the break. This does not apply to Data Depot or home directories -- only scratch storage.

Have a wonderful break, everyone, and we look forward to great things in the new year!

We will provide an update by 8pm.

We will provide an update by 8pm.

We will provide an update by 1:00 PM.

Engineers were able to trace the load to a specific set of cluster jobs and processes performing highly suboptimal access patterns to the filesystem. After these misconfigured jobs were terminated, the load on Data Depot servers has returned to normal levels and performance of Data Depot was restored.

As always, but particularly during this period of limited metadata capacity, we strongly recommend researchers to avoid performing heavy I/O operations against the Data Depot filesystem. Carrying out most of your intermediate processing in highly-performant cluster scratch spaces (and only copying final results to Data Depot at the end) will likely yield a much higher overall throughput. Please reach out to us if you would like to discuss your lab data workflows and brainstorm possible enhancements to them.

We greatly appreciate your patience and understanding during this transition period. Please contact rcac-help@purdue.edu if you have any questions or concerns.

Engineers are currently diagnosing the issue and are working to identify a fix. Job scheduling has been paused while this issue is being addressed.

We will provide an update by 2pm.

All systems will return to full production by Sunday, August 1st, 2021 at 12:00pm EDT.

Any SLURM jobs which request a walltime which would take them past the above times will not start and will remain in the queue until after the maintenance is completed.

System engineers are actively engaged with the vendor to troubleshoot and fix the glitch. We appreciate your patience and will provide another update by 9pm.

Any SLURM jobs which request a walltime which would take them past Tuesday, May 11th, 2021 at 5:00pm EDT will not start and will remain in the queue until after the maintenance is completed.

We will provide an update by 10 pm.

We will provide an update by 9:00 PM today.