Cluster Installation: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 187: Line 187:
On bl1upper which qmaster node install using install_qmaster
On bl1upper which qmaster node install using install_qmaster


<pre
<pre>
root@bl1upper:/usr/share/gridengine 5>./install_qmaster
root@bl1upper:/usr/share/gridengine 5>./install_qmaster
</pre>
</pre>
Line 193: Line 193:
Most of the answers are yes/no or typing enter.
Most of the answers are yes/no or typing enter.


Follwoing important environment variables are written to /usr/share/gridengine/default/common/settings.csh which should be in the $PATH.
Following important environment variables are written to /usr/share/gridengine/default/common/settings.csh which should be in the $PATH.


$SGE_ROOT=/usr/share/gridengine
$SGE_ROOT=/usr/share/gridengine
Line 200: Line 200:
$SGE_CELL=default
$SGE_CELL=default


There is an option to give administrative email which is very useful, when ever there is any problem gridengine will send error messages to email.
Following things need to be decided before installation
Ready with a file contains admin and submit hosts or you can manually enter all the hosts separated by space, use full DNS names of hosts. In this installation shadow host is not used. After the shadow host step make sure allhosts group and all.q are created otherwise installation sge_execd will have problems. Scheduler Tuning selected as 'Max', it has disadvantage, gridengine immediately schedules with out assuming the load, this will cause successive job submissions will go to same host until all the slots are filled for that machine. Selecting 'Normal' will assume the load but there is overhead of few sec. extra time for job scheduling.  
 
* There is an option to give administrative email which is very useful, when ever there is any problem gridengine will send error messages to email.
* Ready with a file contains admin and submit hosts or you can manually enter all the hosts separated by space, use full DNS names of hosts.  
* In this installation shadow host is not used.  
* After the shadow host step make sure allhosts group and all.q are created otherwise installation sge_execd will have problems.  
* Scheduler Tuning selected as 'Max', it has disadvantage, gridengine immediately schedules with out assuming the load, this will cause successive job submissions will go to same host until all the slots are filled for that machine. Selecting 'Normal' will assume the load but there is overhead of few sec. extra time for job scheduling.
 


After finishing the installation the configuration files are automatically written to the directory /usr/share/gridengine/default since the cell name selected is 'default'. This directory can be choosen as a shared directory over NFS. Otherwise copy this directory to every host used int the cluster.
After finishing the installation the configuration files are automatically written to the directory /usr/share/gridengine/default since the cell name selected is 'default'. This directory can be choosen as a shared directory over NFS. Otherwise copy this directory to every host used int the cluster.
Line 211: Line 217:


the input is almost typing return if you already copied the 'default' directory to this node.
the input is almost typing return if you already copied the 'default' directory to this node.
== Restarting sgemaster ==
When grid engine installed first time /etc/init.d/sgemaster and /etc/init.d/sge_execd services are automatically installed.
If you want to restart sgemaster make sure all the sge_execd deamons are stoped. You can do this by following commands
<pre>
service sge_execd stop
service sgemaster stop
</pre>
for starting
<pre>
service sge_execd start
service sgemaster start
</pre>
When ever work stations need to be restarted make sure sgemaster work station started first. To keep the services restarted automatically during the startup make sure chkconfig is on.
<pre>
chkconfig sgemaster on
chkconfig sge_execd on
</pre>


== Son of Gridengine ==
== Son of Gridengine ==
38

edits