Hi Jeff, I don't think we ever open-sourced pmclusterd since it was
(at the time) SGI ICE specific,
so it's unlikely anyone outside SGI will know much about it.
This is the daemon that aggregates indoms for per-cluster-node CPU
data on the head node, so
the client tools just monitor the head node, right? If that's the tool
framework you're referring to,
I always thought it was a bit of an abomination of the indom concept
(even though I wrote it!),
but designed it that way to be more scalable than monitoring every
cluster node individually.
WHat issues are you running in to?
Regards
-- Mark
On Thu, Sep 1, 2016 at 2:43 AM, Jeff Hanson <jhanson@xxxxxxx> wrote:
> As we (SGI) explore what to do about the scaling issues with pmclusterd
> as it is currently written I am exploring other options. For cluster
> configurations are people generally running pmcd locally on the cluster
> nodes
> and logging to the node? Running pmcd locally on the cluster node with
> another system as the logger? Other thoughts?
>
> Thanks.
> --
> -----------------------------------------------------------------------
> Jeff Hanson - jhanson@xxxxxxx - Senior Technical Support Engineer
>
> You can choose a ready guide in some celestial voice.
> If you choose not to decide, you still have made a choice.
> You can choose from phantom fears and kindness that can kill;
> I will choose a path that's clear
> I will choose freewill. - Peart
>
> _______________________________________________
> pcp mailing list
> pcp@xxxxxxxxxxx
> http://oss.sgi.com/mailman/listinfo/pcp
|