[
https://issues.apache.org/jira/browse/OOZIE-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974661#comment-15974661
]
Peter Bacsko commented on OOZIE-2843:
-------------------------------------
+1 thanks [~andras.piros], committed to master
> 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
> Fix For: 5.0.0
>
> Attachments: OOZIE-2843.001.patch, OOZIE-2843.002.patch,
> OOZIE-2843.003.patch, OOZIE-2843.004.patch, OOZIE-2843.005.patch,
> OOZIE-2843.006.patch, OOZIE-2843.007.patch
>
>
> 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)
