General Euler Courtesy

  • Interactive jobs should be kept to a 30 minute maximum.
  • Don’t build extremely large projects on the head node.
  • It is preferred that home directories stay below 1.5TiB in size.
    • du -sh ~ shows the size of your home directory.
  • Please set a time limit on jobs – it allows the scheduler to operate more efficiently.
  • Please log out when you are not using Euler.

A Few Stricter Rules

  • The maximum size for a home directory is no greater than 2.5TiB.
  • All computational jobs should be executed through Slurm. Users who frequently run computations on the login node may have their account disabled without notice.

Job Cleanup

  • Slurm jobs should exit gracefully within 2 minutes of being cancelled or preempted.
    • Jobs which are cancelled or preempted will be sent a SIGTERM by the Slurm daemon.
  • Jobs which launch background tasks should ensure that those tasks are cancelled upon completion of the job. The Slurm daemon is usually able to do this automatically, but unexpected behavior on the part of a third-party utility or service is always possible.
  • Users who frequently submit jobs which exhibit poor cancellation behavior may have restrictions placed on their accounts.

Creating and Accessing Temporary Files

  • Files and folders created under /tmp or /scratch may be deleted without warning when their parent filesystem is nearing its storage limit.
  • Jobs which do not exit cleanly may create orphaned temporary directories. Users who frequently submit such jobs may receive restrictions on their file creation privileges.

Priority Hours and Accounts

  • Hardware contributors can debit their share of hours to have access to a higher-priority queue with the identifier groupname.
  • In order to use the priority queue, you need to pass the following flags along with your script
    • --account=groupname
    • -p groupname
    • --qos=groupname_owner
  • Replace groupname with the name of your lab or PI (e.g. sbel or zavalab)
  • To ensure that hours are not debited accidentally, the default behavior is not to use any elevated priority levels when submitting a job.
  • Jobs can also be scheduled with elevated priority on the default queue. Submitting in this way will give the job a higher priority when scheduling, but will not cause the preemption of lower-priority jobs. This is accomplished with the following flags
    • --account=groupname
    • --qos=priority