How to Migrate qmaster to Another Host Using a Script

How to Migrate qmaster to Another Host Using a Script

Note Because the spooling database cannot be located on an NFS-mounted file system, the following procedure requires that you use the Berkeley DB RPC server for spooling. If you configure spooling to a local file system, you must transfer the spooling database to a local file system on the new sge_qmaster host.

1. Check that the new master host has read/write access.
   The new master host must have read/write access to the qmaster spool directory and common directory as does the current master. If the administrative user is the root user (check the global cluster configuration for the setting of admin_user), you should verify that the root user can create files in these directories under the root user name.
   
   
2. Run the migration script on the new master host.
   On the new master host, type the following command as the root user:

   # $SGE_ROOT/$SGE_CELL/common/sgemaster -migrate
   

   This command stops sge_qmaster on the old master host and starts it on the new master host. The master host name listed in the file $SGE_ROOT/$SGE_CELL/common/act_qmaster is automatically changed to the new master host. If qmaster is not running, warning messages will appear and a delay of about one minute will occur until qmaster is started on the new host.
   
   

3. Modify the shadow_masters file if necessary.
   1. Check if the $SGE_ROOT/$SGE_CELL/common/shadow_masters file exists.
      If the file exists, you can add the new qmaster host to this file and remove the old master host, depending on your requirements.
   2. Then stop and restart the sge_shadowd daemons by issuing the following commands on the respective machines:
      

      $SGE_ROOT/$SGE_CELL/common/sgemaster -shadowd stop
      $SGE_ROOT/$SGE_CELL/common/sgemaster -shadowd