Editing CommunityData:Hyak Ikt (Deprecreated)
From CommunityData
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
To use Hyak, you must first have a UW NetID, access to Hyak, and a two factor authentication token. Details on getting set up with all three are available at [[CommunityData:Hyak setup]]. | To use Hyak, you must first have a UW NetID, access to Hyak, and a two factor authentication token. Details on getting set up with all three are available at [[CommunityData:Hyak setup]]. | ||
== Setting up SSH == | == Setting up SSH == | ||
When you connect to SSH, it will ask you for a key from your token. Typing this in every time you start a connection be a pain. One approach is to create an .ssh config file that will create a "tunnel" the first time you connect and send all subsequent connections to Hyak over that tunnel. Some details [ | When you connect to SSH, it will ask you for a key from your token. Typing this in every time you start a connection be a pain. One approach is to create an .ssh config file that will create a "tunnel" the first time you connect and send all subsequent connections to Hyak over that tunnel. Some details [https://sig.washington.edu/itsigs/Logging_In#SSH_Config_File in the Hyak documentation]. | ||
I've added the following config to the file <code>~/.ssh/config</code> on my laptop (you will want to change the username): | I've added the following config to the file <code>~/.ssh/config</code> on my laptop (you will want to change the username): | ||
Host | Host hyak hyak.washington.edu | ||
User makohill | User makohill | ||
HostName | HostName login3.hyak.washington.edu | ||
ControlPath ~/.ssh/master-%r@%h:%p | ControlPath ~/.ssh/master-%r@%h:%p | ||
ControlMaster auto | ControlMaster auto | ||
Line 40: | Line 31: | ||
It will prompt you for your UWNetID's password and your PRN which is the little number that comes from your token. | It will prompt you for your UWNetID's password and your PRN which is the little number that comes from your token. | ||
== Setting | == Setting Up Hyak == | ||
When setting up Hyak, you must first add | When setting up Hyak, you must first add this to your BASHRC file. Generally, you can simply edit the following file on Hyak: <code>~/.bashrc</code> | ||
## hyak | ## hyak specific options | ||
alias rgrep='grep -r' | |||
alias big_machine='qsub -W group_list=hyak-mako -l walltime=500:00:00,mem=200gb -I' | |||
alias any_machine='qsub -W group_list=hyak-mako -l walltime=500:00:00,mem=100gb -I' | |||
PYTHON_PATH="/com/local/lib/python3.4:$PYTHON_PATH" | |||
LD_LIBRARY_PATH="/com/local/lib:$LD_LIBRARY_PATH" | |||
PKG_CONFIG_PATH=/com/local/lib/pkgconfig:/usr/share/pkgconfig | |||
MC_CORES=16 | |||
PATH="/com/local/bin:$PATH" | |||
module load revolutionr_7.2 | |||
module load parallel_sql | module load parallel_sql | ||
umask 007 | umask 007 | ||
The final line is particularly important. If you do not do this, the files you create on Hyak will be able to be read or written by others in the group! | The final line is particularly important. If you do not do this, the files you create on Hyak will be able to be read or written by others in the group! | ||
Line 77: | Line 58: | ||
These lines will mean that if I have "checked out" an interactive machine, I can ssh from my computer to Hyak and then directly through an addition hop to the machine (like ssh n0652). Those ForwardX11 lines means if I graph things on this window, they will open on my local display. | These lines will mean that if I have "checked out" an interactive machine, I can ssh from my computer to Hyak and then directly through an addition hop to the machine (like ssh n0652). Those ForwardX11 lines means if I graph things on this window, they will open on my local display. | ||
== Running Jobs on Hyak == | == Running Jobs on Hyak == | ||
When you first log in to Hyak, you will be on a "login node". These are nodes that have access to the Internet, and can be used to update code, move files around, etc. They should not be used for computationally intensive tasks. To actually run jobs, there are a few different options, described in detail [https://sig.washington.edu/itsigs/Hyak_Job_Scheduler in the itSigs documentation]. Following are basic instructions for the two most common use cases. | |||
When you first log in to Hyak, you will be on a "login node". These are nodes that have access to the Internet, and can be used to update code, move files around, etc. They should not be used for computationally intensive tasks. To actually run jobs, there are a few different options, described in detail [https://sig.washington.edu/itsigs/Hyak_Job_Scheduler in the itSigs documentation]. Following are basic instructions for | |||
=== Interactive nodes === | === Interactive nodes === | ||
Line 120: | Line 69: | ||
=== Parallel SQL === | === Parallel SQL === | ||
For big jobs you will want to use multiple nodes. Hyak has a very cool tool that makes this very easy, called Parallel SQL. Detailed instructions are in [https://sig.washington.edu/itsigs/Hyak_parallel-sql the itsigs parallel-sql documentation]. There is also a | For big jobs you will want to use multiple nodes. Hyak has a very cool tool that makes this very easy, called Parallel SQL. Detailed instructions are in [https://sig.washington.edu/itsigs/Hyak_parallel-sql the itsigs parallel-sql documentation]. There is also a full walkthrough example with instructions in the <code>wikiresearch/hyak_example</code> directory. | ||
The basic workflow is: | The basic workflow is: | ||
1. Prepare the code, and test it with a single file (either on your computer, or on an interactive node). | 1. Prepare the code, and test it with a single file (either on your computer, or on an interactive node). | ||
2. Write a job_script file. This tells the node what job to run. There is an example on the Parallel SQL wiki page (linked above), and an example in the wikiresearch/hyak_example directory. | 2. Write a job_script file. This tells the node what job to run. There is an example on the Parallel SQL wiki page (linked above), and an example in the wikiresearch/hyak_example directory. | ||
3. Create a task_list file. This is a list of commands that should be run, with one line per file that the command should operate on. An example file might look something like: | 3. Create a task_list file. This is a list of commands that should be run, with one line per file that the command should operate on. An example file might look something like: | ||
Line 152: | Line 92: | ||
$ for job in $(seq 1 N); do qsub job_script; done | $ for job in $(seq 1 N); do qsub job_script; done | ||
# N is the number of nodes | # N is the number of nodes | ||
=== Killing jobs on compute nodes === | === Killing jobs on compute nodes === | ||
Line 203: | Line 99: | ||
For example, you might run <tt>nodestate</tt> from a login node to figure out the ID number for your job (let's say it's 12345), then run <tt>mjobctl -c 12345</tt> to send a SIGTERM signal or <tt>mjobctl -F 12345</tt> to send a SIGKILL signal that will bring job 12345 to an end. | For example, you might run <tt>nodestate</tt> from a login node to figure out the ID number for your job (let's say it's 12345), then run <tt>mjobctl -c 12345</tt> to send a SIGTERM signal or <tt>mjobctl -F 12345</tt> to send a SIGKILL signal that will bring job 12345 to an end. | ||
Note that only four user accounts at a time can have the bits necessary to kill other people's jobs, so while you can do this on your own jobs, you'll need to bother the IRC channel to find help cancelling other's jobs | Note that only four user accounts at a time can have the bits necessary to kill other people's jobs, so while you can do this on your own jobs, you'll need to bother the IRC channel to find help cancelling other's jobs. Also, check out the [http://docs.adaptivecomputing.com/maui/commands/mjobctl.php documentation for mjobctl] for more info. |