(Click to open topic with navigation)

Appendix H: Running multiple TORQUE servers and MOMs on the same node

TORQUE can be configured to allow multiple servers and MOMs to run on the same node. This example will show how to configure, compile and install two different TORQUE servers and moms on the same node. For details, see these topics:

• Configuring the first TORQUE
• Configuring the second TORQUE
• Bringing the first TORQUE server online
• Bringing the second TORQUE server online

Configuring the first TORQUE

Then make and make install will place the first TORQUE into /usr/spool/PBS1 with the executables in their corresponding directories.

Configuring the second TORQUE

Then make and make install will place the second TORQUE into /usr/spool/PBS2 with the executables in their corresponding directories.

Bringing the first TORQUE server online

Each command, including pbs_server and pbs_mom, takes parameters indicating which servers and ports to connect to or listen on (when appropriate). Each of these is documented in their corresponding man pages (configure with --enable-docs).

In this example the first TORQUE server will accept batch requests on port 35000, communicate with the MOMs on port 35001, and communicate via RPP on port 35002. The first TORQUE MOM will try to connect to the server on port 35000, it will listen for requests from the server on port 35001 and will communicate via RPP on port 35002. (Each of these command arguments is discussed in further details on the corresponding man page. In particular, -t create is only used the first time a server is run.)

Afterwards, when using a client command to make a batch request it is necessary to specify the server name and server port (35000):

Submitting jobs can be accomplished using the -q option ([queue][@host[:port]]):

Bringing the second TORQUE server online

In this example the second TORQUE server will accept batch requests on port 36000, communicate with the MOMS on port 36002, and communicate via RPP on port 36002. The second TORQUE MOM will try to connect to the server on port 36000, it will listen for requests from the server on port 36001 and will communicate via RPP on port 36002.

Afterward, when using a client command to make a batch request it is necessary to specify the server name and server port (36002):

© 2012 Adaptive Computing