[jira] [Commented] (OOZIE-1817) Oozie timers are not biased
[ https://issues.apache.org/jira/browse/OOZIE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14036594#comment-14036594 ] Mona Chitnis commented on OOZIE-1817: - Had offline discussion to clarify usage of the cron counters - ".execute", ".acquireLock" and ".call" common to all commands and ".materialize" for the Materialize Command. No changes there except for some cleanup. +1 > Oozie timers are not biased > --- > > Key: OOZIE-1817 > URL: https://issues.apache.org/jira/browse/OOZIE-1817 > Project: Oozie > Issue Type: Improvement > Components: monitoring >Affects Versions: 4.0.0 >Reporter: Gilad Wolff >Assignee: Robert Kanter > Attachments: OOZIE-1817.patch, OOZIE-1817.patch, OOZIE-1817.patch, > OOZIE-1817.patch, OOZIE-1817.patch, OOZIE-1817.patch, OOZIE-1817.patch, > OOZIE-1817.patch, counters.jpg, gauges.jpg, histograms.jpg, json.txt, > meters.jpg, timers.jpg > > > Oozie timers are not biased, that is, the statistical metrics they expose are > over the run-time of the Oozie server instead of a window of time. This makes > them not very useful especially after the server has been running for a while > (codehale has very efficient and easy to use biased histograms that can be > used instead). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (OOZIE-1817) Oozie timers are not biased
[ https://issues.apache.org/jira/browse/OOZIE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14033164#comment-14033164 ] Robert Kanter commented on OOZIE-1817: -- Test failures are unrelated, javac warning is expected. [~chitnis], do I still have your +1 from RB after [these minor changes|https://issues.apache.org/jira/browse/OOZIE-1817?focusedCommentId=14032865&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14032865]? > Oozie timers are not biased > --- > > Key: OOZIE-1817 > URL: https://issues.apache.org/jira/browse/OOZIE-1817 > Project: Oozie > Issue Type: Improvement > Components: monitoring >Affects Versions: 4.0.0 >Reporter: Gilad Wolff >Assignee: Robert Kanter > Attachments: OOZIE-1817.patch, OOZIE-1817.patch, OOZIE-1817.patch, > OOZIE-1817.patch, OOZIE-1817.patch, OOZIE-1817.patch, OOZIE-1817.patch, > OOZIE-1817.patch, counters.jpg, gauges.jpg, histograms.jpg, json.txt, > meters.jpg, timers.jpg > > > Oozie timers are not biased, that is, the statistical metrics they expose are > over the run-time of the Oozie server instead of a window of time. This makes > them not very useful especially after the server has been running for a while > (codehale has very efficient and easy to use biased histograms that can be > used instead). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (OOZIE-1817) Oozie timers are not biased
[
https://issues.apache.org/jira/browse/OOZIE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14033141#comment-14033141
]
Hadoop QA commented on OOZIE-1817:
--
Testing JIRA OOZIE-1817
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+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:green}+1{color} the patch does adds/modifies 4 testcase(s)
{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:red}-1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:red}-1{color} the patch seems to introduce 1 new javac warning(s)
{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: 1480
.Tests failed: 3
.Tests errors: 1
.The patch failed the following testcases:
.
testPauseBundleAndCoordinator(org.apache.oozie.service.TestPauseTransitService)
.
testUnpauseBundleAndCoordinator(org.apache.oozie.service.TestPauseTransitService)
.
testResetSequence_withMultiThread(org.apache.oozie.service.TestZKUUIDService)
{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/1322/
> Oozie timers are not biased
> ---
>
> Key: OOZIE-1817
> URL: https://issues.apache.org/jira/browse/OOZIE-1817
> Project: Oozie
> Issue Type: Improvement
> Components: monitoring
>Affects Versions: 4.0.0
>Reporter: Gilad Wolff
>Assignee: Robert Kanter
> Attachments: OOZIE-1817.patch, OOZIE-1817.patch, OOZIE-1817.patch,
> OOZIE-1817.patch, OOZIE-1817.patch, OOZIE-1817.patch, OOZIE-1817.patch,
> OOZIE-1817.patch, counters.jpg, gauges.jpg, histograms.jpg, json.txt,
> meters.jpg, timers.jpg
>
>
> Oozie timers are not biased, that is, the statistical metrics they expose are
> over the run-time of the Oozie server instead of a window of time. This makes
> them not very useful especially after the server has been running for a while
> (codehale has very efficient and easy to use biased histograms that can be
> used instead).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (OOZIE-1817) Oozie timers are not biased
[ https://issues.apache.org/jira/browse/OOZIE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14014093#comment-14014093 ] Mona Chitnis commented on OOZIE-1817: - I agree we can get rid of the meters. they are not useful at the moment since our logging levels are not quite perfect, and also errors/warns here can be due to myriad reasons - user definitions etc, and do not necessarily pinpoint to system issues. the JSON attachment show useful metrics around locks and times they were held. That will be useful. taking a second look at code now > Oozie timers are not biased > --- > > Key: OOZIE-1817 > URL: https://issues.apache.org/jira/browse/OOZIE-1817 > Project: Oozie > Issue Type: Improvement > Components: monitoring >Affects Versions: 4.0.0 >Reporter: Gilad Wolff >Assignee: Robert Kanter > Attachments: OOZIE-1817.patch, OOZIE-1817.patch, OOZIE-1817.patch, > OOZIE-1817.patch, OOZIE-1817.patch, OOZIE-1817.patch, OOZIE-1817.patch, > counters.jpg, gauges.jpg, histograms.jpg, json.txt, meters.jpg, timers.jpg > > > Oozie timers are not biased, that is, the statistical metrics they expose are > over the run-time of the Oozie server instead of a window of time. This makes > them not very useful especially after the server has been running for a while > (codehale has very efficient and easy to use biased histograms that can be > used instead). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (OOZIE-1817) Oozie timers are not biased
[
https://issues.apache.org/jira/browse/OOZIE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010863#comment-14010863
]
Hadoop QA commented on OOZIE-1817:
--
Testing JIRA OOZIE-1817
Cleaning local git workspace
{color:red}-1{color} Patch failed to apply to head of branch
> Oozie timers are not biased
> ---
>
> Key: OOZIE-1817
> URL: https://issues.apache.org/jira/browse/OOZIE-1817
> Project: Oozie
> Issue Type: Improvement
> Components: monitoring
>Affects Versions: 4.0.0
>Reporter: Gilad Wolff
>Assignee: Robert Kanter
> Attachments: OOZIE-1817.patch, OOZIE-1817.patch, OOZIE-1817.patch,
> OOZIE-1817.patch, OOZIE-1817.patch, OOZIE-1817.patch, OOZIE-1817.patch,
> counters.jpg, gauges.jpg, histograms.jpg, json.txt, meters.jpg, timers.jpg
>
>
> Oozie timers are not biased, that is, the statistical metrics they expose are
> over the run-time of the Oozie server instead of a window of time. This makes
> them not very useful especially after the server has been running for a while
> (codehale has very efficient and easy to use biased histograms that can be
> used instead).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (OOZIE-1817) Oozie timers are not biased
[ https://issues.apache.org/jira/browse/OOZIE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010802#comment-14010802 ] Robert Kanter commented on OOZIE-1817: -- Cool, the screenshots worked. The json.txt file didn't, but it's in the list of attachments at the top of the page. > Oozie timers are not biased > --- > > Key: OOZIE-1817 > URL: https://issues.apache.org/jira/browse/OOZIE-1817 > Project: Oozie > Issue Type: Improvement > Components: monitoring >Affects Versions: 4.0.0 >Reporter: Gilad Wolff >Assignee: Robert Kanter > Attachments: OOZIE-1817.patch, OOZIE-1817.patch, OOZIE-1817.patch, > OOZIE-1817.patch, OOZIE-1817.patch, OOZIE-1817.patch, OOZIE-1817.patch, > counters.jpg, gauges.jpg, histograms.jpg, json.txt, meters.jpg, timers.jpg > > > Oozie timers are not biased, that is, the statistical metrics they expose are > over the run-time of the Oozie server instead of a window of time. This makes > them not very useful especially after the server has been running for a while > (codehale has very efficient and easy to use biased histograms that can be > used instead). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (OOZIE-1817) Oozie timers are not biased
[ https://issues.apache.org/jira/browse/OOZIE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010586#comment-14010586 ] Mona Chitnis commented on OOZIE-1817: - did a first run of the patch on RB. But wait for more reviews before patch update. Also, can you attach a screenshot of the web-console if possible? > Oozie timers are not biased > --- > > Key: OOZIE-1817 > URL: https://issues.apache.org/jira/browse/OOZIE-1817 > Project: Oozie > Issue Type: Improvement > Components: monitoring >Affects Versions: 4.0.0 >Reporter: Gilad Wolff >Assignee: Robert Kanter > Attachments: OOZIE-1817.patch, OOZIE-1817.patch, OOZIE-1817.patch, > OOZIE-1817.patch, OOZIE-1817.patch, OOZIE-1817.patch, OOZIE-1817.patch > > > Oozie timers are not biased, that is, the statistical metrics they expose are > over the run-time of the Oozie server instead of a window of time. This makes > them not very useful especially after the server has been running for a while > (codehale has very efficient and easy to use biased histograms that can be > used instead). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (OOZIE-1817) Oozie timers are not biased
[
https://issues.apache.org/jira/browse/OOZIE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14008057#comment-14008057
]
Hadoop QA commented on OOZIE-1817:
--
Testing JIRA OOZIE-1817
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+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:green}+1{color} the patch does adds/modifies 4 testcase(s)
{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:red}-1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:red}-1{color} the patch seems to introduce 1 new javac warning(s)
{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: 1456
.Tests failed: 1
.Tests errors: 2
.The patch failed the following testcases:
.
testCoordinatorActionCommandsSubmitAndStart(org.apache.oozie.sla.TestSLAEventGeneration)
{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/1258/
> Oozie timers are not biased
> ---
>
> Key: OOZIE-1817
> URL: https://issues.apache.org/jira/browse/OOZIE-1817
> Project: Oozie
> Issue Type: Improvement
> Components: monitoring
>Affects Versions: 4.0.0
>Reporter: Gilad Wolff
>Assignee: Robert Kanter
> Attachments: OOZIE-1817.patch, OOZIE-1817.patch, OOZIE-1817.patch,
> OOZIE-1817.patch, OOZIE-1817.patch, OOZIE-1817.patch, OOZIE-1817.patch
>
>
> Oozie timers are not biased, that is, the statistical metrics they expose are
> over the run-time of the Oozie server instead of a window of time. This makes
> them not very useful especially after the server has been running for a while
> (codehale has very efficient and easy to use biased histograms that can be
> used instead).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (OOZIE-1817) Oozie timers are not biased
[ https://issues.apache.org/jira/browse/OOZIE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003814#comment-14003814 ] Robert Kanter commented on OOZIE-1817: -- test failures unrelated javac warning has to do with adding a new endpoint to the array of endpoints in admin so it's okay. > Oozie timers are not biased > --- > > Key: OOZIE-1817 > URL: https://issues.apache.org/jira/browse/OOZIE-1817 > Project: Oozie > Issue Type: Improvement > Components: monitoring >Affects Versions: 4.0.0 >Reporter: Gilad Wolff >Assignee: Robert Kanter > Attachments: OOZIE-1817.patch, OOZIE-1817.patch, OOZIE-1817.patch, > OOZIE-1817.patch, OOZIE-1817.patch, OOZIE-1817.patch > > > Oozie timers are not biased, that is, the statistical metrics they expose are > over the run-time of the Oozie server instead of a window of time. This makes > them not very useful especially after the server has been running for a while > (codehale has very efficient and easy to use biased histograms that can be > used instead). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (OOZIE-1817) Oozie timers are not biased
[
https://issues.apache.org/jira/browse/OOZIE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003628#comment-14003628
]
Hadoop QA commented on OOZIE-1817:
--
Testing JIRA OOZIE-1817
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+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:green}+1{color} the patch does adds/modifies 4 testcase(s)
{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:red}-1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:red}-1{color} the patch seems to introduce 1 new javac warning(s)
{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: 1455
.Tests failed: 5
.Tests errors: 2
.The patch failed the following testcases:
.
testCoordStatusTransitServiceSuspendedBottomUp(org.apache.oozie.service.TestStatusTransitService)
.
testCoordStatusTransitServiceForTimeout(org.apache.oozie.service.TestStatusTransitService)
.
testCoord_throwException(org.apache.oozie.command.coord.TestCoordChangeXCommand)
.
testCoordinatorActionCommandsSubmitAndStart(org.apache.oozie.sla.TestSLAEventGeneration)
.
testTimeOutWithUnresolvedMissingDependencies(org.apache.oozie.command.coord.TestCoordPushDependencyCheckXCommand)
{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/1247/
> Oozie timers are not biased
> ---
>
> Key: OOZIE-1817
> URL: https://issues.apache.org/jira/browse/OOZIE-1817
> Project: Oozie
> Issue Type: Improvement
> Components: monitoring
>Affects Versions: 4.0.0
>Reporter: Gilad Wolff
>Assignee: Robert Kanter
> Attachments: OOZIE-1817.patch, OOZIE-1817.patch, OOZIE-1817.patch,
> OOZIE-1817.patch, OOZIE-1817.patch, OOZIE-1817.patch
>
>
> Oozie timers are not biased, that is, the statistical metrics they expose are
> over the run-time of the Oozie server instead of a window of time. This makes
> them not very useful especially after the server has been running for a while
> (codehale has very efficient and easy to use biased histograms that can be
> used instead).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (OOZIE-1817) Oozie timers are not biased
[
https://issues.apache.org/jira/browse/OOZIE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13999730#comment-13999730
]
Hadoop QA commented on OOZIE-1817:
--
Testing JIRA OOZIE-1817
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+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:green}+1{color} the patch does adds/modifies 4 testcase(s)
{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: 1454
.Tests failed: 3
.Tests errors: 2
.The patch failed the following testcases:
. testJobLog(org.apache.oozie.client.TestOozieCLI)
.
testCoordinatorActionCommandsSubmitAndStart(org.apache.oozie.sla.TestSLAEventGeneration)
.
testBundleEngineKill(org.apache.oozie.servlet.TestV1JobServletBundleEngine)
{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/1241/
> Oozie timers are not biased
> ---
>
> Key: OOZIE-1817
> URL: https://issues.apache.org/jira/browse/OOZIE-1817
> Project: Oozie
> Issue Type: Improvement
> Components: monitoring
>Affects Versions: 4.0.0
>Reporter: Gilad Wolff
>Assignee: Robert Kanter
> Attachments: OOZIE-1817.patch, OOZIE-1817.patch, OOZIE-1817.patch,
> OOZIE-1817.patch
>
>
> Oozie timers are not biased, that is, the statistical metrics they expose are
> over the run-time of the Oozie server instead of a window of time. This makes
> them not very useful especially after the server has been running for a while
> (codehale has very efficient and easy to use biased histograms that can be
> used instead).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (OOZIE-1817) Oozie timers are not biased
[
https://issues.apache.org/jira/browse/OOZIE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13995971#comment-13995971
]
Hadoop QA commented on OOZIE-1817:
--
Testing JIRA OOZIE-1817
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+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:green}+1{color} the patch does adds/modifies 4 testcase(s)
{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: 1447
.Tests failed: 2
.Tests errors: 4
.The patch failed the following testcases:
.
testCoordinatorActionCommandsSubmitAndStart(org.apache.oozie.sla.TestSLAEventGeneration)
.
testTimeOutWithUnresolvedMissingDependencies(org.apache.oozie.command.coord.TestCoordPushDependencyCheckXCommand)
{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/1231/
> Oozie timers are not biased
> ---
>
> Key: OOZIE-1817
> URL: https://issues.apache.org/jira/browse/OOZIE-1817
> Project: Oozie
> Issue Type: Improvement
> Components: monitoring
>Affects Versions: 4.0.0
>Reporter: Gilad Wolff
>Assignee: Robert Kanter
> Attachments: OOZIE-1817.patch, OOZIE-1817.patch, OOZIE-1817.patch
>
>
> Oozie timers are not biased, that is, the statistical metrics they expose are
> over the run-time of the Oozie server instead of a window of time. This makes
> them not very useful especially after the server has been running for a while
> (codehale has very efficient and easy to use biased histograms that can be
> used instead).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (OOZIE-1817) Oozie timers are not biased
[
https://issues.apache.org/jira/browse/OOZIE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13994077#comment-13994077
]
Hadoop QA commented on OOZIE-1817:
--
Testing JIRA OOZIE-1817
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+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:green}+1{color} the patch does adds/modifies 4 testcase(s)
{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} - patch does not compile, cannot run testcases
{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/1226/
> Oozie timers are not biased
> ---
>
> Key: OOZIE-1817
> URL: https://issues.apache.org/jira/browse/OOZIE-1817
> Project: Oozie
> Issue Type: Improvement
> Components: monitoring
>Affects Versions: 4.0.0
>Reporter: Gilad Wolff
>Assignee: Robert Kanter
> Attachments: OOZIE-1817.patch, OOZIE-1817.patch
>
>
> Oozie timers are not biased, that is, the statistical metrics they expose are
> over the run-time of the Oozie server instead of a window of time. This makes
> them not very useful especially after the server has been running for a while
> (codehale has very efficient and easy to use biased histograms that can be
> used instead).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (OOZIE-1817) Oozie timers are not biased
[
https://issues.apache.org/jira/browse/OOZIE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13994802#comment-13994802
]
Hadoop QA commented on OOZIE-1817:
--
Testing JIRA OOZIE-1817
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+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:green}+1{color} the patch does adds/modifies 4 testcase(s)
{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} - patch does not compile, cannot run testcases
{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/1227/
> Oozie timers are not biased
> ---
>
> Key: OOZIE-1817
> URL: https://issues.apache.org/jira/browse/OOZIE-1817
> Project: Oozie
> Issue Type: Improvement
> Components: monitoring
>Affects Versions: 4.0.0
>Reporter: Gilad Wolff
>Assignee: Robert Kanter
> Attachments: OOZIE-1817.patch, OOZIE-1817.patch
>
>
> Oozie timers are not biased, that is, the statistical metrics they expose are
> over the run-time of the Oozie server instead of a window of time. This makes
> them not very useful especially after the server has been running for a while
> (codehale has very efficient and easy to use biased histograms that can be
> used instead).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (OOZIE-1817) Oozie timers are not biased
[ https://issues.apache.org/jira/browse/OOZIE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13988259#comment-13988259 ] Robert Kanter commented on OOZIE-1817: -- I think for this we should transition to the Codahale Metrics library; it also provides a bunch of other useful things that we could maybe take advantage of. The API looks pretty similar to what we're already using, so switch to it shouldn't be too hard. Of course, for compatibility, we'll keep the current Instrumentation, but eventually we could get remove of it. > Oozie timers are not biased > --- > > Key: OOZIE-1817 > URL: https://issues.apache.org/jira/browse/OOZIE-1817 > Project: Oozie > Issue Type: Improvement > Components: monitoring >Affects Versions: 4.0.0 >Reporter: Gilad Wolff >Assignee: Robert Kanter > > Oozie timers are not biased, that is, the statistical metrics they expose are > over the run-time of the Oozie server instead of a window of time. This makes > them not very useful especially after the server has been running for a while > (codehale has very efficient and easy to use biased histograms that can be > used instead). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (OOZIE-1817) Oozie timers are not biased
[ https://issues.apache.org/jira/browse/OOZIE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13988261#comment-13988261 ] Robert Kanter commented on OOZIE-1817: -- Here's info on the Metrics library: http://metrics.codahale.com/getting-started/ > Oozie timers are not biased > --- > > Key: OOZIE-1817 > URL: https://issues.apache.org/jira/browse/OOZIE-1817 > Project: Oozie > Issue Type: Improvement > Components: monitoring >Affects Versions: 4.0.0 >Reporter: Gilad Wolff >Assignee: Robert Kanter > > Oozie timers are not biased, that is, the statistical metrics they expose are > over the run-time of the Oozie server instead of a window of time. This makes > them not very useful especially after the server has been running for a while > (codehale has very efficient and easy to use biased histograms that can be > used instead). -- This message was sent by Atlassian JIRA (v6.2#6252)
