Two owners for the same cluster service !!!!

Hi,

I have configured a two node failover cluster with the minimum hardware
configuration ie..two nodes, a shared scsi disk with gfs on it and a
n/w between the two nodes.
I compiled the cluster suite source downloaded from the redhat ftp site
against linux-2.6.12 kernel and have used the system-config-cluster gui
to generate the cluster.conf file. I am not using clvm,but instead I
have directly used gfs_mkfs on the scsi disk itself. I have tried the
following two scenarios -

1. I created two failover domains, giving opposite priorities to both
the nodes in each of the domains. Then I created a resource of type gfs
corresponding to the shared scsi disk and a corresponding cluster
service of type gfs and attached it to one of the failover domain.

2. I created an unrestricted failover domain with only one node in it
and created a resource of type gfs corresponding to the shared scsi
disk and a correspondig cluster service of type gfs and attached it to
the failover domain.

I have used manual fencing in both the scenarios and the recovery
policy of the service is relocate and the service is to be autostarted.

Now, whenever I use the steps to bring up the cluster on both the nodes
as follows -
service ccsd start
service cman start
service fenced start
service gfs start
service rgmanager start,

after the last step, the status as seen by the system-config-cluster on
both the nodes says that the service is started. However on individual
nodes it says that the owner of the service is that node and the
previous owner is none.. ie both of the nodes seem to be the owner of
the service.

Shouldn't only one node be the owner of a service in a failover cluster
at one time?? Also how can I induce node failure so that the service
failovers to the other node and restarts there??

Thanks in advance for the help...
Please ask in case you need any more details.

Maverick

.

Relevant Pages

  • Re: Why Cluster in a test Environment?
    ... If your apps are not failover aware, ... SQL Server 2000 then takes anywhere from 30 seconds to minutes before ... a cluster but not appear in a standalone server. ... A non-clustered environment would not allow accurate stress testing do ...
    (microsoft.public.sqlserver.clustering)
  • Re: Is there a best practise to implement a warm standby-solution
    ... Doing all this on a failover cluster is just adding complexity. ... I suspected that some of what I need is not provided by MSCS. ... ApplicationX is cluster aware. ...
    (microsoft.public.windows.server.clustering)
  • Re: Configure failover in seconds
    ... When a failover starts, it starts. ... "pause" because of your san disks who need to failover. ... add this script as a resource to your cluster ... Is this done in CLuster Administrator? ...
    (microsoft.public.windows.server.clustering)
  • Re: Configure failover in seconds
    ... When a failover starts, it starts. ... add this script as a resource to your cluster ... Is this done in CLuster Administrator? ... before failover occurs from one node to another in Windows Server ...
    (microsoft.public.windows.server.clustering)
  • Re: Virtual Server and Cluster
    ... Manual shutdown of a host is a special case for failover, and there is a section in that document which describes a simple batch file which runs on shutdown that essentially stops the cluster service. ... Virtual Server per MS documentation and it is working fine. ...
    (microsoft.public.windows.server.clustering)