UCMDB Tip: Why do we need locking mechanism in UD?
UD 10.0 introduced a number of jobs that support the workflow capabilities, such as Inventory Discovery and UD Agent Management jobs.
During the operation of such jobs each step of the workflow can be retried with a significant delay between the retries. There are a number of scenarios where several of such discovery jobs can attempt to run on the same node at the same time. For example, several jobs can be activated via the Discovery Jobs/Modules mode or the same Node can belong to multiple Mangement Zones with the same rank both having Inventory Acitivity enabled, multiple UCMDB servers discovering the same Node, etc.
To ensure the correct operation of the workflow, the first job that runs its workflow attempts to lock the node to prevent other jobs from operating on the node and potentially interfering with the operation of the current job. For example, the Inventory Discovery by Scanner before running the scanner have to set the scanner configuration, once the scanner is finished, it needs to collect the matching local scan file, etc.
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”
Click the KUDOS star on the left to say 'Thanks'