Skip to main content

January 2026 Maintenance Update

· 5 min read
Kristen Finch
Director of Research Computing Solutions

During this month’s scheduled maintenance window, we completed several system upgrades and routine updates across Klone and Tillicum to improve stability, performance, and security. The next maintenance is scheduled for Tuesday, February 10, 2026 (the second Tuesday of the month).

Notable Updates

In addition to routine image updates and security patches, we upgraded:

  • Klone login node process enforcement to Arbiter 3 and paused user notifications and Klone and Tillicum (read more below).
  • Klone has been upgraded from cgroups v1 to cgroups v2. This upgrade shouldn't be a noticeable for most users, but in some cases memory accounting under cgroups v2 is unified and includes all file-backed page cache. This difference may make memory usage appear higher or "inflated" compared to v1 in niche cases and some specific Java-based applications.
  • Slurm version 25.11.1 on both clusters.
  • Duo 2FA on Klone (Tillicum already up to date). This change aligns with ongoing UW security upgrades.
Action Required

All University of Washington technology users must update Duo Mobile to version 4.85.0 or later on all registered devices by February 2, 2026. Users who cannot update their devices must register a platform authenticator, a new phone/tablet, or request a hardware token from UWIT. The Duo phone call authentication method is being phased out by the University and no longer available for logging into Klone or Tillicum. 

Check your device’s Duo Mobile application version.

Login Node Usage & Arbiter Enforcement (Important Reminder)

Login nodes are shared community resources intended for:

  • Transferring data
  • Navigating the filesystem
  • Editing and developing code
  • Submitting jobs to the scheduler

As part of this maintenance, Klone was upgraded to Arbiter 3, a tool which automates login node monitoring and enforces usage limits to ensure stability and ensure fair access.

Arbiter monitors resource usage on login nodes and will:

  • Slow or halt processes that exceed permitted thresholds.
  • Terminate processes outright if necessary.

Arbitor email notifications halted

Previously, users received email notifications for each offending process when Arbiter thresholds were exceeded. We have found these notifications are not an effective way to communicate our policies. To avoid notification fatigue, we have stopped sending these emails.

This does not mean enforcement has stopped. Arbiter continues to actively limit, halt, or kill processes on login nodes as needed.

Be a good HPC-citizen - do not connect to a login node

Connecting directly to the login node using tools like VS Code Remote-SSH frequently leads to Arbiter intervention and could cause login node instability since background server processes persist beyond an active session.

Instead, follow our recommended best practices and set up your ProxyJump to connect your local VS Code to Klone or use the streamlined option offered by our Open OnDemand interactive application for VS Code.

Winter 2026 Computing Workshops

Stay informed by subscribing to our mailing list and the UW-IT Research Computing Events Calendar.

Office Hours

Additional Training Opportunities

Having trouble? Get Research Computing support.

Happy Computing,

Hyak Team