[ClusterLabs] Q: crm_mon "Statck:" columns

Techs-yama tecabu at gmail.com
Mon Dec 21 00:34:52 EST 2020


Thank you for your reply.
I've learned a lot.
best regards.

2020年12月18日(金) 3:22 Ken Gaillot <kgaillot at redhat.com>:

> On Thu, 2020-12-17 at 21:20 +0900, Techs-yama wrote:
> > Hello there,
> >
> > This is probably a fairly rudimentary question.
> > I recently started studying corosync and pacemaker.
> >
> > I have a question about how to recognize heartbeat or corosync status
> > type.
> > Where does the "Stack:" columns recognize for configurations when run
> > the crm_mon command?
> > [root at host1 ~]# crm_mon
> > ============
> > Last updated: hoge hoge
> > Stack: Heartbeat
> >
> >
> > Is this be configured in corosync or heartbeat?
>
> Support for particular cluster layers ("stacks") is determined when
> Pacemaker is built. Pacemaker 2.0.0 and later only supports corosync 2
> and later, so it's always and only "corosync" now, but Pacemaker 1
> could also optionally support heartbeat and corosync 1 (with either
> CMAN or the pacemaker plugin).
>
> Out of whichever stacks are supported, Pacemaker dynamically determines
> which one is currently in use when it starts. So basically, it's not
> determined from a configuration file, but based on what's running.
>
> > e.g.) service directive on corosync.conf?
> > service {
> >     name: pacemaker
> >     ver: 0
> >     use_mgmtd: yes
> > }
> >
> > and then service-directive parameters are mandatory sections for
> > configurations?
> >
> > best regards.
> --
> Ken Gaillot <kgaillot at redhat.com>
>
> _______________________________________________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> ClusterLabs home: https://www.clusterlabs.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clusterlabs.org/pipermail/users/attachments/20201221/fb4ed247/attachment.htm>


More information about the Users mailing list