Mailing List Archive: Linux-HA: Pacemaker

Design question. Service running everywhere

Index | Next | Previous | View Threaded

cer.inet at linuxmail

Jun 12, 2012, 1:17 PM

Post #1 of 2 (150 views)
Permalink

Design question. Service running everywhere

Hi there!

I've some questions for you.

I'm deploying a new cluster with a service inside that doesn't matter.
The important of the service is that is running in everywhere by it's
own internal functionality.
So start/stop the resource in a given node is the same that doing it
in the rest. All nodes will suffer that start/stop effect.

This is causing me some issues with Pacemaker.

As far as I know, pacemaker monitor the resource in each node (in this
case /etc/init.d/service status, because it's an LSB resource).
But /etc/init.d/service status will return the same as long as the
service is the same in all nodes.

I don't know if working with clones will give some advantages. I need
pacemaker to manage IPVs and other stuff.

Shall I not use pacemaker with this service? Or, do I need some
special configuration or design options?

Best regards.

--
/* Arturo Borrero Gonzalez || cer.inet [at] linuxmail */
/* Use debian gnu/linux! Best OS ever! */

_______________________________________________
Pacemaker mailing list: Pacemaker [at] oss
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

andreas at hastexo

Jun 12, 2012, 3:13 PM

Post #2 of 2 (144 views)
Permalink

Re: Design question. Service running everywhere [In reply to]

On 06/12/2012 10:17 PM, Arturo Borrero Gonzalez wrote:
> Hi there!
>
> I've some questions for you.
>
> I'm deploying a new cluster with a service inside that doesn't matter.
> The important of the service is that is running in everywhere by it's
> own internal functionality.
> So start/stop the resource in a given node is the same that doing it
> in the rest. All nodes will suffer that start/stop effect.
>
> This is causing me some issues with Pacemaker.
>
> As far as I know, pacemaker monitor the resource in each node (in this
> case /etc/init.d/service status, because it's an LSB resource).
> But /etc/init.d/service status will return the same as long as the
> service is the same in all nodes.
>
> I don't know if working with clones will give some advantages. I need
> pacemaker to manage IPVs and other stuff.

Yes, that LSB service running on all nodes is a typical scenario for an
anonymous cloned resource.

Regards,
Andreas

--
Need help with Pacemaker?
http://www.hastexo.com/now

>
> Shall I not use pacemaker with this service? Or, do I need some
> special configuration or design options?
>
> Best regards.
>

Attachments:

signature.asc (0.22 KB)

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads