[
https://issues.apache.org/jira/browse/OOZIE-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16820324#comment-16820324
]
Junfan Zhang commented on OOZIE-3393:
-------------------------------------
[~asalamon74] Sorry, after recheck the test case, i have uploaded patch-4. In
order to use the {{MetricsInstrumentationService.getMetricRegistry}} in the
{{TestCoordMaterializeTriggerService.testCoordMaterializeTriggerService4}}, I
have to change the scope of the {{getMetricRegistry}} method to public.
> 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-3393-3.patch, oozie-3393-4.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)
