[
https://issues.apache.org/jira/browse/OOZIE-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16673733#comment-16673733
]
Prabhu Joseph commented on OOZIE-3373:
--------------------------------------
[~andras.piros] Attached a patch with fixing the lock information. Can you
review this when you get some time.
> Logging of lock information inconsistent
> ----------------------------------------
>
> Key: OOZIE-3373
> URL: https://issues.apache.org/jira/browse/OOZIE-3373
> Project: Oozie
> Issue Type: Bug
> Components: core
> Affects Versions: 4.3.0
> Reporter: Prabhu Joseph
> Assignee: Prabhu Joseph
> Priority: Minor
> Attachments: OOZIE-3373-1.patch
>
>
> The lock resource name getEntityKey() is printed when lock is acquired
> whereas getName() + "_" + actionId is printed when Could not get lock. This
> makes difficult to correlate the logs.
> {code}
> LOG.debug("Acquired lock for [{0}] in [{1}]", getEntityKey(), getName());
> LOG.debug("Could not get lock [{0}], timed out [{1}]ms, and requeue itself
> [{2}]", this.toString(),
> getLockTimeOut(), getName());
> {code}
> Example:
> {code}
> 2018-10-10 12:00:05,698 pool-6-thread-5 DEBUG ActionCheckXCommand:526 -
> SERVER[dn3-george] USER[-] GROUP[-] TOKEN[-] APP[-] JOB[-]
> ACTION[0000134-181002155022081-oozie-oozi-W@shell1] Could not get lock
> [action.check_0000134-181002155022081-oozie-oozi-W@shell1], timed out
> [5,000]ms, and requeue itself [action.check]
> {code}
> The actual lock it waits is for 0000134-181002155022081-oozie-oozi-W which is
> not printed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
