The Blade List pane provides the primary interface to monitoring servers and their activity. Unlike the Job List pane, which receives real-time updates from the Engine, the blade list is refreshed in bulk either manually or by a timer managed by the Dashboard. A manual refresh is triggered by selecting the blade list icon in the toolbar.
By default, the blade list is automatically refreshed every 60 seconds. This value can be changed in the preferences pane. At large sites the amount of data returned from this query can be quite large, so a reload interval should be selected with care to avoid network bottlenecks.
The Blade List pane responds to several mouse operations:
Clicking on any row will cause information about the selected blade to be displayed in the Blade Info pane, below the Blade List pane.
The Blade List pane also responds to standard multi-click controls. This is typically useful in conjunction with a context senstive menu select.
Right-clicking (or Control-click) will bring up a context sensitive menu that allows you to operate on the selected blades.
Clear Earlier Blade Data
Tells the engine to remove the selected blades from memory. This is a good way to clear out blades which were started, but are no longer active. If an active blade is cleared it will re-appear when it checks in with the engine.
NIMBY Restriction (On | Off)
Sends a request to the selected blades to set their NIMBY (Not-In-My-Backyard) mode. When NIMBY is set "on" a blade will only accept work from jobs that were spooled from that host, typically a user's desktop. NIMBY "off" allows any jobs that match the usual profile criteria to be accepted. Note that it is possible to restrict the mode to a specific user as well, through an http directive to the blade.
The assignment tracer provides a mechanism to help debug when blades are not picking up new tasks.
When selecting a blade and choosing "Assignment Tracer" from the context menu, a tracer dialog will open. It will remain blank until the selected blade requests a job from the engine. The engine will then document how it traces through the existing jobs to determine whether or not to give work to the blade.
This history is detailed in the tracer dialog as shown above. In this trace we see that several jobs had no dispatchable tasks, and one job required a specific (different) host.
The following keyboard shortcuts are available in the Blade List pane:
Selects all blades.
Refreshes the blade list.