Re: clustat on GULM

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Entered a bug.

Bugzilla Bug 250811: clustat report wrong information about rgmanager on a GULM cluster

Hope it will be solved soon, which can save some work of mine, since I can not trust/rely on clustat right now.

Thanks,

Siman

On 8/2/07, Lon Hohberger <lhh@xxxxxxxxxx> wrote:
On Tue, Jul 31, 2007 at 10:22:33AM -0400, siman hew wrote:
> I found clustat report wrong information about rgmanager when a cluster is
> GULM.
> I setup a 3-node cluster on RHEL4U5, with GULM.  There are one failover
> domain, one resource and one service, just for testing.
> I found clustat always report rgmanger is running after cluster is started.
> With the configuration with DLM, clustat report correctly.
> node4 is lock server, and all nodes report the same inaccurate information.

GULM doesn't have a way to provide sub-groups really, except for users
of lockspaces.

Can you file a bugzilla about this?  I wonder if we can get the
information for "what nodes are in this lockspace" from GULM.  If it's
possible, we could probably fix it.

--
Lon Hohberger - Software Engineer - Red Hat, Inc.

--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux