[
https://issues.apache.org/jira/browse/OOZIE-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14961566#comment-14961566
]
Robert Kanter commented on OOZIE-2251:
--------------------------------------
I was just running the relevant unit tests, and it looks like
{{TestMetricsInstrumentation}} has a bunch of failures now. [~nperiwal], can
you take a look and make a new patch? I promise I won't take as long to review
it this time :)
Looks like they're all failing with
{noformat}
testInstrumentationTimer(org.apache.oozie.util.TestMetricsInstrumentation)
Time elapsed: 0.012 sec <<< ERROR!
java.lang.NullPointerException
at
org.apache.oozie.service.ConfigurationService.getBoolean(ConfigurationService.java:524)
at
org.apache.oozie.util.MetricsInstrumentation.<init>(MetricsInstrumentation.java:105)
at
org.apache.oozie.util.TestMetricsInstrumentation.testInstrumentationTimer(TestMetricsInstrumentation.java:62)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:243)
at junit.framework.TestSuite.run(TestSuite.java:238)
at
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:24)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{noformat}
> Expose instrumental matrices in Realtime Graphing tool
> ------------------------------------------------------
>
> Key: OOZIE-2251
> URL: https://issues.apache.org/jira/browse/OOZIE-2251
> Project: Oozie
> Issue Type: New Feature
> Components: monitoring
> Reporter: Jaydeep Vishwakarma
> Assignee: Narayan Periwal
> Attachments: OOZIE-2251-v0.patch, OOZIE-2251-v1.patch,
> OOZIE-2251-v10.patch, OOZIE-2251-v2.patch, OOZIE-2251-v3.patch,
> OOZIE-2251-v4.patch, OOZIE-2251-v5.patch, OOZIE-2251-v6.patch,
> OOZIE-2251-v7.patch, OOZIE-2251-v8.patch, OOZIE-2251-v9.patch
>
>
> We have been logging so many important matrices in oozie-instrumentation.log
> . These information is very useful for oozie functional monitoring. But it is
> always difficult to get the meaning from flat file. If we expose this
> information on some graphing tool, We can get the lot of meaning out of it
> and can take some actions based on it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
