[GENIUS-62] lock-manager-impl floods logs with OptimisticLockFailedExceptions

Mon, 14 May 2018 14:44:29 +0000

{message=Optimistic lock failed., errorList=[RpcError [message=Optimistic lock failed., severity=ERROR, errorType=APPLICATION, tag=resource-denied, applicationTag=null, info=null, cause=org.opendaylight.yangtools.yang.data.api.schema.tree.ConflictingModificationAppliedException: Node was created by other transaction.]]}

As per definition in Logging Best Practices, this should be a WARN, as there is a retry mechanism in place.

I am not familiar with the design of the lock manager, but it seems it could be using EntityOwnershipService, which already provides cluster-wide exclusive locking.

If the exceptions are direct result of application design and retries are expected, the message should be lowered to debug.

OpenDaylight JIRA

[GENIUS-62] lock-manager-impl floods logs with OptimisticLockFailedExceptions