Hi
I thought that the status was called by V1 mode of Heartbeat.
However, status calls monitor in /etc/ha.d/resource.d/hto-mapfuncs.
---
hto-mapfuncs:56
status) $__SCRIPT_NAME monitor;;# Mapping this
to monitor is a bug
---
Is the status processing an unnecessar
Hi
Pacemaker-1.0 moves in the following versions.
I think that I do not move in the latest edition.
http://hg.clusterlabs.org/pacemaker/pygui/rev/18332eae086e
Tomo
2011/3/9 Jakob Curdes
>
> > Hi,
> >
> > you have to decide: heartbeat OR corosync. It makes no sense to install
> both
> > cluster
Hi,
I sent a half-finished email. I'm sorry.
FYI,I dont simply that from my experience.
> 2 and 4 node clusters running 1.0.x should easily handle 200 resources or
so.
> Clusters running >= 1.1.4 should be able to go even higher.
12 and 16 node clusters not running from pm-1.0.x(12 * 16 = 192).
Hi,
FYI,I dont simply that from my experience.
2 and 4 node clusters running 1.0.x should easily handle 200 resources or
so.
Clusters running >= 1.1.4 should be able to go even higher.
10resource
Regards,
Tomo
2010/12/9 Andrew Beekhof
> On Thu, Dec 9, 2010 at 9:06 AM, Alain.Moulle
> wrote: