pcp
[Top] [All Lists]

Re: [pcp] pmlogger -u questions

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: [pcp] pmlogger -u questions
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Tue, 15 Apr 2014 01:39:49 -0400 (EDT)
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <534B4330.1060008@xxxxxxxxxxxxxxxx>
References: <01e901cf56df$4ce97de0$e6bc79a0$@internode.on.net> <1665962954.4723287.1397437104781.JavaMail.zimbra@xxxxxxxxxx> <534B4330.1060008@xxxxxxxxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: E/7p6T51djhmAHFVAZxUUDuBSn0z/w==
Thread-topic: pmlogger -u questions
Hi Ken,

----- Original Message -----
> [...]
> The issue is real, but I'm obviously not explaining it well enough.
> [...]
> Let me try with an annotated example.

BTW - thanks for the detailed explanation, this got me on the same page
as you now I think.

> am not sure there will be QA coverage, because the issue is a design
> problem, rather than a bug in implementation.

OK.  It sounds possible that "kill -9" on an active logger, followed
by replay/logcheck may be able to induce the failures of the current
code, and demonstrate quantifiable improvements.  Maybe not reliable
failure cases, but with sufficient iterations/entropy/gamma-rays, we
should be able to build confidence in any changes.

> Neither of these problems are new.  But as we inch towards a unified
> context of some sort, and before that pmNewContext accepting a directory
> name as an argument for PM_CONTEXT_ARCHIVE it is going to become a more
> pressing matter.

Ayup, sounds good.

--
Nathan

<Prev in Thread] Current Thread [Next in Thread>