Ikt Hyak Cluster Decommissioning
The older Ikt cluster will be completely decommissioned in June 2020. Ikt users and groups, please begin making preparations now. Details are available HERE.
Sign up for the Hyak-users mailing list to stay up to date with the latest news: https://mailman1.u.washington.edu/mailman/listinfo/hyak-users
This list is used for ALL announcements to Hyak users, so please sign up. Important Hyak announcements are ONLY sent to this list, not to the individual Hyak accounts.
You can get to this top level page using the address: http://wiki.hyak.uw.edu
Hyak consists of two independent clusters: ikt.hyak (hyak classic) and mox.hyak (hyak next-gen).
ikt.Hyak is online.
mox.Hyak is online.
Hyak will be offline from 9:00 am - 5:00 pm for scheduled maintenance the second Tuesday of every month. Every third month (Feb, May, Aug, Nov), the maintenance window will last from 9:00 am to 9:00 the following morning. More on the Maintenance schedule.
Other maintenance performed on Hyak is relatively rare, short (30 - 60 minutes), and does not impact running jobs. This type of maintenance is announced to the hyak-users list.
Cluster Node Status
We run the Ganglia cluster status tool on ikt.hyak. Here you can find out the details about the CPU, memory, and network usage of the nodes in your allocation. (Ganglia does not run on mox.hyak.)
Hyak is a service of UW-IT. You can read more about it in the Service Catalog.
This link has information about of some the research groups which use Hyak: Hyak_Research
Here is a list of some of the research papers which have used Hyak: Hyak Publications
Most of the nodes are devoted for computing but the cluster also includes a few "login-nodes", dedicated to logins, file transfers, and similar communication tasks. There are also nodes that belong to the sponsoring institutions, and nodes for compiling and testing the programs.
Any UW student can get access to hyak by joining the RC club: http://students.washington.edu/hpcc/getting-started-on-hyak/
RC Club office hours: http://students.washington.edu/hpcc/calendar/
Hyak consists of two independent clusters: ikt.hyak (hyak classic) and mox.hyak (hyak next-gen). All new nodes are added to mox.hyak.
ikt.hyak has hundreds of nodes, each comparable to a high-end server. A typical node on ikt.hyak has 16 processor cores and at least 64GB of memory. All the ikt.hyak nodes run CentOS 6 Linux, and they are tied together by the Slurm cluster software. The user tasks are submitted through Slurm scheduler. ikt.Hyak is made of several generations of hardware with different levels of performance, see Hyak Node Hardware for more details.
mox.hyak contains hundreds of nodes, each comparable to a high-end server. A typical node on mox.hyak has 28 processor cores and at least 128GB of memory. All the mox.hyak nodes run CentOS 7 Linux, and they are tied together by the Slurm cluster software. The user tasks are submitted through Slurm scheduler.
For an overview of mox please see Hyak mox Overview.
Purchasing Hyak Capacity
CPU and storage options are available for purchase to Hyak users associated with sponsored campus units. New nodes will be part of mox.hyak.
This information is provided for preliminary planing purposes only. Please contact firstname.lastname@example.org for assistance in preparing actual Hyak hardware configurations.
Please review everything in this section before contacting Hyak support for help with new accounts. This section also contains useful information on life with two-factor authentication, including setting up SSH tunnels to reduce hassles.
You should be familiar with the Linux command line. Hyak's default shell is bash which is also the default shell on a Mac computer. Here is a link to Software Carpentry's lessons on the bash shell, Python, git etc. (Scroll down for videos of their courses.)
Software Carpentry also conducts workshops at UW. See below link for the next workshop at UW:
You should be familiar with Hyak basics:
Before you start running your code to hyak, ensure it works on your own computer, or even better, in your lab network. Be sure you know how to keep all the cores busy. For example, using GNU Parallel for weak-scaling, or MPI for strong-scaling.
A user connects to hyak by using ssh. Mac and Linux machines have ssh. Windows users will have to install appropriate ssh software.
Software and Development Tools
Hyak provides software development tools and libraries for HPC and data intensive computing.
Filesystems and Data Transfer
Hyak offers a variety of filesystems, each best suited for a different set of circumstances. Along with selecting the best filesystem for the job, this section includes instructions for moving your data to and from Hyak.
Submitting and Running Jobs
All Hyak use is mediated by the system scheduler. This section provides details on using the scheduler to run interactive, batch, and parallel jobs. It also includes instructions for using the scheduler to monitor your jobs and the cluster status.
ikt.hyak uses the slurm scheduler. Jobs must be submitted via login nodes.
mox.hyak uses the slurm scheduler. Jobs must be submitted via the login nodes.
Below page is for both ikt.hyak and mox.hyak.
If you use the STF (Student Technology Fee) allocation, please join the mailing list for the RC club (http://students.washington.edu/hpcc/) and direct all questions there. Do not contact UW-IT for support.
The principle means of support we provide is this Wiki - a comprehensive set of documentation covering all basic Hyak functions. If you encounter problems with one of Hyak's basic functions send an e-mail to email@example.com with 'hyak' as the first word in the subject and a brief description of your issue. If you do not use your UW provided e-mail account, please include your UW NetID in your e-mail. If you're reporting a problem with a job or the job scheduler, please include at least one affected jobid as well as paths to the job script and job stdout.
RC Club Office Hours: http://students.washington.edu/hpcc/calendar/
We operate Hyak as a campus resource for research computing at scale. It provides a capable, stable platform upon which users can build complex, domain specific software environments and workflows. Our end-user support resources are limited, covering the system hardware, operating system, filesystems, networks, job scheduler, and a defined set of development tools and applications. Users are responsible for building, installing, maintaining and running any other applications.
To have a good experience using Hyak, or any other HPC/supercomputer system, we offer these general recommendations:
For users building complex codes from sources, please read this.
Here are a few tutorials written for different tasks. While not directly applicable to all users' work, they're worth taking a look at to get an idea about how some common tasks are accomplished using Hyak.
- Compiling HDF5: compiling a non-parallel application with the Intel compilers
- Compiling an MPI application: compiling a test program with the Intel compilers and Intel MPI and then submitting a job to the scheduler
- Hyak HOWTO is a list of articles for different tasks, including how to use Python, Matlab and R on hyak.
Hyak wiki pages Index
Below is a list of Hyak wiki pages which do not start with the word Hyak.
Please review this online course if you are not already familiar with *nix systems:
The Teragrid offers an excellent online tutorial series on more advanced HPC topics. You must create an account before accessing content. Just follow the instructions on the main page.
Hyak User Contributions
Hyak users can contribute and find tips from other users on the Hyak User Contributions site.
- Wish List - requests for software features
Citing Hyak in Publications and Proposals
Please remember to acknowledge Hyak in any publications or posters with results Hyak contributed to generating. When citing Hyak please use the following language:
- This work was facilitated though the use of advanced computational, storage, and networking infrastructure provided by the Hyak supercomputer system at the University of Washington
When you cite Hyak, please let us know! Send mail to firstname.lastname@example.org with Hyak as the first word in the subject along with a citation we can use in the body of the message. Likewise please let know of successful funding proposals and research collaborations which relied, at least in part, on Hyak for their success.
Here's a current list of publications citing Hyak.