[
https://issues.apache.org/jira/browse/OOZIE-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098222#comment-15098222
]
Hadoop QA commented on OOZIE-2433:
----------------------------------
Testing JIRA OOZIE-2433
Cleaning local git workspace
----------------------------
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
. {color:green}+1{color} the patch does not introduce any @author tags
. {color:green}+1{color} the patch does not introduce any tabs
. {color:green}+1{color} the patch does not introduce any trailing spaces
. {color:green}+1{color} the patch does not introduce any line longer than
132
. {color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
. {color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
. {color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
. {color:green}+1{color} HEAD compiles
. {color:green}+1{color} patch compiles
. {color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
. {color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
. {color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
. Tests run: 1704
. Tests failed: 4
. Tests errors: 0
. The patch failed the following testcases:
. testPurgeXCommandFailed(org.apache.oozie.command.TestPurgeXCommand)
. testPurgeWFWithSubWF1(org.apache.oozie.command.TestPurgeXCommand)
. testForNoDuplicates(org.apache.oozie.event.TestEventGeneration)
. testSamplers(org.apache.oozie.util.TestMetricsInstrumentation)
{color:green}+1 DISTRO{color}
. {color:green}+1{color} distro tarball builds with the patch
----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/2710/
> oozie restart required if oozie metrics to graphing tool broken
> ---------------------------------------------------------------
>
> Key: OOZIE-2433
> URL: https://issues.apache.org/jira/browse/OOZIE-2433
> Project: Oozie
> Issue Type: Bug
> Reporter: Sanjeev T
> Assignee: Narayan Periwal
> Attachments: OOZIE-2433.patch
>
>
> When we start oozie service it starts emitting oozie metrics, expose to the
> host
> * oozie.external_monitoring.address
> If we have issue on the external host or service disruption for a while, the
> metrics are not exposed, it requires oozie restart
> * Can we avoid oozie restart, let oozie do health check and expose metrics
> * Enable logging for the oozie metrics emitting to external host
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
