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 QubeGUI or the commandline WranglerView UI or by command-line calls to qblock and qbunlock.
Locking/Unlocking with the Qube! WranglerView
In the QubeGUIWranglerView, 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 so it , which stops those processes immediately and then requeues them on other machines.
qblock host [host,…]
qbunlock host [host,…]
where host is a list of one more host names.
--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 --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.
% qblock % qblock myhost
% qblock % qblock --range 0, 1 sb005
For more information see the qblock and qbunlock sections in the Commandline Command Line Reference section of the Qube Users ! Render Wrangler's Guide or using the
"--help" option to qblock/qbunlock.