Anchor | ||||
---|---|---|---|---|
|
Qube ! manages this tagging through a system of "locks" that effectively 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 QubeGUI or the commandline calls to qblock and qbunlock.
Locking/Unlocking with the Qube
...
WranglerView
In WranglerViewthe QubeGUI, 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 "Purge running jobs" from the machine , which so it stops those processes immediately and then requeues them on other machines.
...
qblock and qbunlock can be used to lock and unlock one or more slots on the specified host(s):
qblock host [host,…]
qbunlock host [host,…]
where host is a list of one more host names.
The A --all
flag can be used in place of the hostname. When using the --all
flag, only hosts which match the other criteria are operated upon:
qblock --all
qblock --cluster /myCluster --all all
qbunlock --active --all
By default, qblock locks out all of the subjob slots on the host, but you can also quantify the number of slots to lock or unlock:
...
where rangespec is either a slot number, a comma-delimited list of slots, a range or some combination.
Example:
% qblock % qblock myhost
% qblock % qblock --range 0, 1 sb005
See Also
For more information see the qblock and qbunlock sections in the Command Line Commandline Reference section of the Qube ! Render Wrangler's Users Guide or using the "--help"
option to qblock/qbunlock.