Jenkins build is back to normal : oozie-trunk-find-patches-available #156197

See

Build failed in Jenkins: oozie-trunk-find-patches-available #156196

See -- Started by timer [EnvInject] - Loading node environment variables. Building remotely on H1 (Hadoop) in workspace

[jira] [Commented] (OOZIE-2457) Oozie log parsing regex consume more than 90% cpu

[ https://issues.apache.org/jira/browse/OOZIE-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15961335#comment-15961335 ] Satish Subhashrao Saley commented on OOZIE-2457: Thanks Robert for review. Committed to

[jira] [Commented] (OOZIE-2827) More directly view of the coordinator’s history from perspective of workflow action.

[ https://issues.apache.org/jira/browse/OOZIE-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15961108#comment-15961108 ] Hadoop QA commented on OOZIE-2827: -- Testing JIRA OOZIE-2827 Cleaning local git workspace

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

[ https://issues.apache.org/jira/browse/OOZIE-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15960994#comment-15960994 ] Hadoop QA commented on OOZIE-2843: -- Testing JIRA OOZIE-2843 Cleaning local git workspace

Jenkins build is back to normal : oozie-trunk-precommit-build #3782

See

[jira] [Updated] (OOZIE-2827) More directly view of the coordinator’s history from perspective of workflow action.

[ https://issues.apache.org/jira/browse/OOZIE-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alonzo Zhou updated OOZIE-2827: --- Attachment: OOZIE-2827-0005.patch > More directly view of the coordinator’s history from perspective

[jira] [Issue Comment Deleted] (OOZIE-2827) More directly view of the coordinator’s history from perspective of workflow action.

[ https://issues.apache.org/jira/browse/OOZIE-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alonzo Zhou updated OOZIE-2827: --- Comment: was deleted (was: Experimental result in real environment： Request: GET

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

[ https://issues.apache.org/jira/browse/OOZIE-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andras Piros updated OOZIE-2843: Attachment: OOZIE-2843.006.patch Addressing review comments. > Enhance logging inside

Re: Review Request 58172: OOZIE-2843 Enhance logging inside ZKLocksService and MemoryLocksService

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58172/ --- (Updated April 7, 2017, 1:31 p.m.) Review request for oozie and Peter Bacsko.

Re: Review Request 58172: OOZIE-2843 Enhance logging inside ZKLocksService and MemoryLocksService

> On April 7, 2017, 10:40 a.m., Peter Bacsko wrote: > > Are we sure LOG.trace() is good? I would vote for DEBUG level. Done. > On April 7, 2017, 10:40 a.m., Peter Bacsko wrote: > > core/src/main/java/org/apache/oozie/service/ZKLocksService.java > > Line 59 (original), 57 (patched) > >

Re: Review Request 58172: OOZIE-2843 Enhance logging inside ZKLocksService and MemoryLocksService

> On ápr. 7, 2017, 10:40 de, Peter Bacsko wrote: > > core/src/main/java/org/apache/oozie/service/ZKLocksService.java > > Lines 164 (patched) > > > > > > One thing that that makes me wonder - what if the lock already

Re: Review Request 58172: OOZIE-2843 Enhance logging inside ZKLocksService and MemoryLocksService

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58172/#review171325 --- Are we sure LOG.trace() is good? I would vote for DEBUG level.

[jira] Subscription: Oozie Patch Available

Issue Subscription Filter: Oozie Patch Available (97 issues) Subscriber: ooziedaily Key Summary OOZIE-2851 spelling mistakes in examples https://issues.apache.org/jira/browse/OOZIE-2851 OOZIE-2849 Fix build warnings when assembling directories