[
https://issues.apache.org/jira/browse/AMBARI-8769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14250544#comment-14250544
]
Hadoop QA commented on AMBARI-8769:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12687821/AMBARI-8769.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/980//console
This message is automatically generated.
> Aggregator checkpoint logic should take into account the checkPointDelay
> ------------------------------------------------------------------------
>
> Key: AMBARI-8769
> URL: https://issues.apache.org/jira/browse/AMBARI-8769
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
> Affects Versions: 2.0.0
> Reporter: Siddharth Wagle
> Assignee: Siddharth Wagle
> Fix For: 2.0.0
>
> Attachments: AMBARI-8769.patch
>
>
> Aggregator checkpoint logic should take into account the checkPointDelay.
> When the checkpoint is saved it is done with a currentTime minus the
> checkPointDelay (this is a configurable value), when it is compared the next
> iteration the checkPointDelay is not taken into account.
> In effect when the delay is the same or greater than interval, aggregator
> will not work.
> Example configuration that should work, and currently is broken (can be
> edited using Ambari on metrics collector service page):
> {noformat}
> timeline.metrics.cluster.aggregator.minute.checkpointCutOffMultiplier = 2
> timeline.metrics.cluster.aggregator.minute.interval = 120
> {noformat}
> Solution:
> Fix the logic that checks if checkpoint is too old
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
