You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2017/10/30 13:40:00 UTC

[jira] [Updated] (SLING-7223) Spikes in RRD after restart

     [ https://issues.apache.org/jira/browse/SLING-7223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Reutegger updated SLING-7223:
------------------------------------
    Attachment: SLING-7223.patch

Attached a patch with proposed changes. Please note, this depends on SLING-7222 and likely requires some manual conflict resolution when applied on top of those changes.

Whenever the RRD4JReporter is initialized or closed, a sample with unknown values is inserted. This indicates to rrdtool (and RRD4J) that no overflow occurred.

> Spikes in RRD after restart
> ---------------------------
>
>                 Key: SLING-7223
>                 URL: https://issues.apache.org/jira/browse/SLING-7223
>             Project: Sling
>          Issue Type: Bug
>          Components: Commons
>    Affects Versions: Commons Metrics RRD4J 1.0.0
>            Reporter: Marcel Reutegger
>         Attachments: SLING-7223.patch
>
>
> Running the reporter for some time and then restarting the process shows spikes in the collected data. These are caused by counter gauges that are reset to zero after a restart. RRD interprets them as 32bit or 64bit integer overflows and calculates incorrect values.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)