You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Junfan Zhang (JIRA)" <ji...@apache.org> on 2019/05/28 07:35:00 UTC
[jira] [Comment Edited] (OOZIE-3393) Add Oozie instrumentation
delayed metric in CoordMaterializeTriggerService
[ https://issues.apache.org/jira/browse/OOZIE-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849416#comment-16849416 ]
Junfan Zhang edited comment on OOZIE-3393 at 5/28/19 7:34 AM:
--------------------------------------------------------------
Sorry, i wrote a bug. Because {{GET_COORD_JOBS_OLDER_FOR_MATERIALIZATION}} only get the id to bean, the metric of mat_delayed_size is always zero.
Now i fix it. Please review the patch [~asalamon74]
was (Author: zuston):
Sorry, i write a bug. Because {{GET_COORD_JOBS_OLDER_FOR_MATERIALIZATION}} only get the id to bean, the metric of mat_delayed_size is always zero.
Now i fix it. Please review the patch [~asalamon74]
> 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
> Fix For: 5.2.0
>
> Attachments: amend-oozie-3393-1.patch, oozie-3393-1.patch, oozie-3393-2.patch, oozie-3393-3.patch, oozie-3393-4.patch, oozie-3393-5.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)