Ravimake sure the flow does not log a warning message to the logs. There is no singleThe multiple lock release issue needs to fixed and if you are the owner of a flow pleaseI have submitted some patches to fix the issue with Live Merge [5], Moving storage domain to maintenance [6] and VdsNotRespondingTreatmentComma5. The Command B's lock has now been released prematurely by Command A.4. Command A continues execution and finally releases the lock the second time3. Command B now acquires the VM lockFor instanceprematurely released for a second command that had acquired the lock which the firstHi All,We have some issues with a few flows on master where the lock acquired is being
released more than once. This could be a real problem in cases where the lock is
command has released.2. The child command releases the lock
1. Command A has acquired the VM lock and executes a child command.The tell tale sign indicating that a flow is one of the offending flows is the warningmessage in the logs indicating that a previously released lock is being released again.I have seen issues with Live Merge [1], Moving storage domain to maintenance[2] ,[org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory- engine-Thread-6) [1435f925] Trying to release exclusive lock which does not exist, lock key: '53cfa6c3-ecd6-4796-84cb- 5c53d7c2a77fVDS_FENCE'
VdsNotRespondingTreatmentCommand [3] and Creating a snapshot [4]. nd [7]. solution to fix the issue, this has be done flow by flow. But below are a few pointers1. If a command has a callback and the command is executing a child command, whichin turn is executing a few child commands. The child command should also have acommand callback so that the locks are released by the framework. Example patch [6]2. If a parent has acquired the lock and is executing a child command with clonedcontext, to make sure that the child does not release the locks acquired by the parentpass the cloned parent context with out locks to the child. Example patch [7]Thanks
_______________________________________________
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel