Computing

User Tools

Site Tools

Trace:
clusterbasics

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
clusterbasics [2016/03/18 14:23]
mgstauff 		clusterbasics [2017/09/25 17:24] (current)
mgstauff [Introduction to The Cluster]
Line 14: Line 14:
 In either case, the job scheduler takes care of finding a compute node to do the actual work of running your batch job or interactive session (both are called 'jobs' by the scheduler, actually). In either case, the job scheduler takes care of finding a compute node to do the actual work of running your batch job or interactive session (both are called 'jobs' by the scheduler, actually).
  
-The cluster is running CentOS 6.3 with Rocks 6.1. This is the software that manages the collection of front and compute nodes, i.e. the cluster - Rocks is //not// the job scheduler. The jobs scheduler is SGE (Actually SoGE, Son of Grid Engine, see below).+The cluster is running CentOS 6.9 (Linux operating system version) with Rocks 6.2 (Cluster management system). This is the software that manages the collection of front and compute nodes, i.e. the cluster - Rocks is //not// the job scheduler. The jobs scheduler is SGE (Actually SoGE, Son of Grid Engine, see below).
  
 ===== General Cluster Diagram ===== ===== General Cluster Diagram =====
Line 38: Line 38:
  
 If you're running something quick like using fslview or ITK-SNAP to look at an image and do simple manipulations, then it's ok to use the front end instead of an interactive job. This actually makes for more efficient use of the compute nodes since you won't be tying up a qlogin session when you're not really use much computational power. Just don't forget to exit your app when you're done. The important thing is not to run computationally intensive jobs on the front end, like using Matlab to run an analysis on some data. If you're running something quick like using fslview or ITK-SNAP to look at an image and do simple manipulations, then it's ok to use the front end instead of an interactive job. This actually makes for more efficient use of the compute nodes since you won't be tying up a qlogin session when you're not really use much computational power. Just don't forget to exit your app when you're done. The important thing is not to run computationally intensive jobs on the front end, like using Matlab to run an analysis on some data.
- 
-__Certain FSL Commands__ 
- 
-Some FSL commands submit their own qsub jobs so must be run from the front end. 
-[[fsl_usage|See details here.]] 
  
 **Limits and TERMINATION** **Limits and TERMINATION**
Line 86: Line 81:
 Home directories are backed up nightly to another location in the data center, but not archived. Only the most recent contents of your home directory are backed up. Home directories are backed up nightly to another location in the data center, but not archived. Only the most recent contents of your home directory are backed up.
  
-===== Jobs Must be Submitted from chead ===== +===== Jobs Can Be Submitted from Nodes ===== 
-All qsub jobs and qlogin sessions must be started from chead. If you try to do either from a compute node, you'll get an error like this:+All ''qlogin'' sessions must be started from chead. 
 + 
 +''qsub'' jobs can be submitted from chead, ''qlogin'' sessions or ''qsub'' jobs. 
 + 
 + If you get an error like this:
  
   denied: host "compute-0-6.local" is no submit host   denied: host "compute-0-6.local" is no submit host
  
 +tell the admins.
clusterbasics.1458310986.txt.gz · Last modified: 2016/03/18 14:23 by mgstauff

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki