Message-ID: <979176003.8721.1711696967876.JavaMail.confluence@host3.pipelinefx.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_8720_2054395267.1711696967875" ------=_Part_8720_2054395267.1711696967875 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html Worker Locking

Worker Locking

When you don't have a dedicated compute farm, it is often nece= ssary to put user's machines into part-time service. So, for example, the h= osts might be available for computing at night, but not during the day. It = can be quite inconvenient to start and stop the Qube! Worker every day. It = would be better if there were a way to simply tag Workers as available or n= ot, depending upon the circumstances.

Qube! manages this tagging through a system of "locks" that ef= fectively control the number of available subjob slots on any Worker host. = Closing out one or more subjob slots is called "locking." This is= controllable from either the WranglerView UI or by command-line calls to <= a href=3D"/display/QUBE/qblock">qblock and qbunlock.

Locking/= Unlocking with the Qube! WranglerView

In WranglerView, the Host Layout provides locking/unlocking capabilities= for the Workers. Right-click on a Worker or Workers and then select one of= the following:

If choosing one of the "Lock" options, decide if you want to &= quot;Purge running jobs" from the machine, which stops those processes= immediately and then requeues them on other machines.

Lock= ing/Unlocking with the command-line utilities

qblock and qbunlock can be used to lock and unlock one or more slots on= the specified host(s):

qblock host [host,=E2=80=A6]
qbunlock host [host,= =E2=80=A6]

where host is a list of one more host names.

The --all flag can be used in place of the hostname.  = When using the --all flag, only hosts which match the other cr= iteria are operated upon: 

qblock --all
qblock --cluster = /myCluster --all
qbunlock --active --all 

By default, qblock locks out all of the subjob slots on the host, but yo= u can also quantify the number of slots to lock or unlock:

qblock --range rangespec host

where rangespec is either a slot number, a comma-deli= mited list of slots, a range or some combination.

Example

% qblock myhost
% qb= lock --range 0, 1 sb005

See Also

For more information see the qblock= and qbunlock sections in the Command Line Reference secti= on of the Qube! Render Wrangler's Guide or using the "--help&quo= t; option to qblock/qbunlock.

------=_Part_8720_2054395267.1711696967875--