You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@oozie.apache.org by "Andras Piros (JIRA)" <ji...@apache.org> on 2017/03/24 08:55:41 UTC

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

Andras Piros created OOZIE-2843:
-----------------------------------

             Summary: 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


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)