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

Re: [Linux-cluster] rgmanager fail to start a 'clone' service, is this a bug or expected behavior?

--- Lon Hohberger <lhh redhat com> wrote:

> On Fri, 2007-01-26 at 08:07 -0800, Roger PeXa
> Escobio wrote:
> > Hi
> > 
> > I am just testing an active-active apache services
> > with Redhat Cluster suit but rgmanager fail to
> start
> > the httpd services in the second server althougt
> it
> > claim it succefully started it ...
> > 
> > I filled a bug :
> >
> > We are running RHEL4.4ES with gfscs from
> centos-4.4
> > 
> > so, is this a bug or an expected behavior?
> Mostly, it's expected behavior; see lengthy
> explanation and example
> outputs of rg_test in the bug.  However:
> (a) rgmanager should log resource collisions, and
> (b) it might be worth investigating having rgmanager
> figure out which
> resources will never collide and allow reuse of
> certain "unique"
> parameters (e.g. mountpoint, in your particular
> case).
thanks a lot

what you write in both bugzilla numbers are very
helpfull, now I understand the problem and how to fix
it, at least for my scenario :-)
(with clvm I can label the filesystem and them trust
the relation "device" <--> "content of device" for
both servers, after that, I can create the FSresource
as shared resources, and then make a reference to them
in each service)
I never realiced the fact that rgmanager "was designed
to allow coexistence of all resources on a single node
for a given configuration" so it is very serious about
collisions ;-)

but I agree about investigating b) because it make
sense to have a cluster with a bunch of sets of nodes
where each set might run services with same mount
point and scripts but different content (/var/www and
httpd <--> website and new-website-version ) ;-)

again, thanks a lot


RedHat Certified Engineer ( RHCE )
Cisco Certified Network Associate ( CCNA )

Don't get soaked.  Take a quick peak at the forecast
with the Yahoo! Search weather shortcut.

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