pcp
[Top] [All Lists]

Re: JSON PMDA

To: Nathan Scott <nathans@xxxxxxxxxx>
Subject: Re: JSON PMDA
From: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
Date: Thu, 16 Apr 2015 18:57:12 -0400
Cc: David Smith <dsmith@xxxxxxxxxx>, Ken McDonell <kenj@xxxxxxxxxxxxxxxx>, pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <973741994.1544247.1429223824192.JavaMail.zimbra@xxxxxxxxxx>
References: <54F9F92D.4010202@xxxxxxxxxx> <448002717.7934024.1427683964254.JavaMail.zimbra@xxxxxxxxxx> <552699FE.7040801@xxxxxxxxxx> <2139482617.15593599.1428634701360.JavaMail.zimbra@xxxxxxxxxx> <552D6524.1030803@xxxxxxxxxx> <y0mfv80ubzj.fsf@xxxxxxxx> <552FD368.6030602@xxxxxxxxxx> <20150416152834.GB6822@xxxxxxxxxx> <973741994.1544247.1429223824192.JavaMail.zimbra@xxxxxxxxxx>
User-agent: Mutt/1.4.2.2i
Hi -

> > ...  but according to normal practice, a "restarted pmda" means
> > "restarted pmcd", which means active pcp contexts are dropped, which
> > means clients are to reconnect & recalculate name->pmid mappings.
> 
> Some more context :- historically (and still now for many PMDAs) a SIGHUP
> to pmcd was the default agent-restart/pmcd-reconfigure mechanism & that'll
> become the default again soon for all PMDAs (so, no loss of connection for
> clients).  [...]

OK, that does change the picture (with respect to demands on the
pmdas, not with respect to expectations by the clients).  I hope it
will not be difficult to audit them.

> Is there any reason not to tackle this problem, Frank?  There's a
> possible solution proposed reusing existing code, & other PMDAs that
> will benefit - seems like a no-brainer that we should Just Do It.

If it's a reasonably small amount of incremental work, agreed.


- FChE

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