[jira] [Updated] (OOZIE-2843) Enhance logging inside ZKLocksService and MemoryLocksService

["Andras Piros (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OOZIE-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andras Piros updated OOZIE-2843:
--------------------------------
    Priority: Minor  (was: Major)

> Enhance logging inside ZKLocksService and MemoryLocksService
> ------------------------------------------------------------
>
>                 Key: OOZIE-2843
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2843
>             Project: Oozie
>          Issue Type: New Feature
>          Components: action, coordinator
>    Affects Versions: 4.3.0
>            Reporter: Andras Piros
>            Assignee: Andras Piros
>            Priority: Minor
>
> Sometimes when Oozie tries to acquire lock [via ZooKeeper|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/service/ZKLocksService.java#L144] or [in-memory|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/service/MemoryLocksService.java] we don't get enough information whether the action succeeded or not. Also other details like retry count, timeout applied, etc. are not logged. Enhancing logging here would benefit debugging of lock handling within {{XCommand}} instances.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)