[
https://issues.apache.org/jira/browse/OOZIE-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16711540#comment-16711540
]
Andras Piros commented on OOZIE-3393:
-------------------------------------
[~zuston] you're welcome. Patch 002 looks good to me thus far. One remaining
point being unit testing.
I'd create new test cases in {{TestCoordMaterializeTriggerService}} with
following semantics:
* setting things up and waiting till a task gets into
{{CoordinatorJob.Status.RUNNING}} [like
this|https://github.com/apache/oozie/blob/master/core/src/test/java/org/apache/oozie/service/TestCoordMaterializeTriggerService.java#L77-L84]
* asserting that the service was instrumented by accessing
{{Services.get().get(InstrumentationService).get().getVariables()}}
> Add Oozie instrumentation delayed metric in CoordMaterializeTriggerService
> --------------------------------------------------------------------------
>
> Key: OOZIE-3393
> URL: https://issues.apache.org/jira/browse/OOZIE-3393
> Project: Oozie
> Issue Type: Improvement
> Components: coordinator
> Reporter: Junfan Zhang
> Assignee: Junfan Zhang
> Priority: Major
> Attachments: oozie-3393-1.patch, oozie-3393-2.patch,
> oozie-instrumentation-1.log
>
>
> We have multiple Oozie scheduled clusters. The problem that is currently
> encountered is that some materialize queues are too late to process during
> the peak hours of the scheduled tasks. We need to get the metrics of the
> delay queue for alarm monitoring and adjust the configuration to optimize.
> Currently we have added metrics for queue size and latency in Oozie
> CoordMaterializeTriggerService class, in order to reflect the general trend
> of current scheduling.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
