pcp
[Top] [All Lists]

[Bug 1296750] incorrect interpolation across <mark> record in a merged a

To: pcp@xxxxxxxxxxx
Subject: [Bug 1296750] incorrect interpolation across <mark> record in a merged archive
From: bugzilla@xxxxxxxxxx
Date: Fri, 08 Jan 2016 19:32:44 +0000
Auto-submitted: auto-generated
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <bug-1296750-355098@xxxxxxxxxxxxxxxxxxx>
References: <bug-1296750-355098@xxxxxxxxxxxxxxxxxxx>
https://bugzilla.redhat.com/show_bug.cgi?id=1296750



--- Comment #1 from Frank Ch. Eigler <fche@xxxxxxxxxx> ---
> or the library should return PM_ERR_VALUE since the interpolated counter
> value is likely to be bogus.

Paraphrasing, you would like to see this happen: ?

pmSetMode(PM_MODE_INTERP ...)
# time = 13:00:20
pmFetch(counter_pmid) -> 15152
# time = 13:00:30 , includes <MARK> this time interval
pmFetch(counter_pmid) -> numvals=0 (missing value), instead of 2794
# time = 13:00:40
pmFetch(counter_pmid) -> 7755
# time = 13:00:50
pmFetch(counter_pmid) -> 12635

Then rate-conversion logic in pmrep/etc. running for the
13:00:30-13:00:40 time interval would result in what
fetchgroups would be represent as a PM_ERR_AGAIN.
(Likewise for the 13:00:20-13:00:30 time interval.)

So libpcp would have to figure out that it's interpolating a
PM_SEM_COUNTER metric across a MARK, and reject it.  (I'm
surprised it's not already doing that.)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=27KwwXhkFQ&a=cc_unsubscribe
<Prev in Thread] Current Thread [Next in Thread>