Re: [pcp] Possible pmmgr issue?

[Ken McDonell <kenj@xxxxxxxxxxxxxxxx>]

I don't seem to have a copy of the original email, so I'm only guessing 
at the context ...
On 13/02/14 23:58, Frank Ch. Eigler wrote:
> Hi -
>
>
> > [...]
> > Note the size of the 2 merge archives.  I need to clean this up,
> > as my rootfs is out of space once more.  Any suggestions on what
> > to look for before I do that?  Thanks.
>  From what I see, it looks like you just happened to catch the machine
> mid-merge, just after the pmcd was lost & restarted, so pmmgr stopped
> & restarted the pmlogger.
>
>
> > -rw-r--r-- 1 pcp pcp 546M Feb 13 14:34 merged-archive-20140213.033222.0
> > -rw-r--r-- 1 pcp pcp  85K Feb 13 14:34 merged-archive-20140213.033222.index
> > -rw-r--r-- 1 pcp pcp 144K Feb 13 14:34 merged-archive-20140213.033222.meta
> > -rw-r--r-- 1 pcp pcp 335M Feb 13 19:43 merged-archive-20140213.084228.0
> > -rw-r--r-- 1 pcp pcp  53K Feb 13 19:43 merged-archive-20140213.084228.index
> > -rw-r--r-- 1 pcp pcp 120K Feb 13 19:43 merged-archive-20140213.084228.meta
> > [iow, this is a small host configuration - yet those logs seem big?]
> I don't know.  pmmgr does not create archives: it's pmlogger and
> pmlogextract, with the documented/saved configurations.
Assuming the pmlogger control file matches the current shipping version, 
then pmlogger is launched with -r which means the expected size for each 
logged metric over the course of 24hrs of logging is reported in 
pmlogger.log (check below /var/log/pcp/pmlogger/<hostname>)
...

pmlogextract cannot make up logger records, so the size of the output 
archive will always be no larger the sum of the input archives.