Using heartbeat? Get help!


Just got this following to a /etc/init.d/heartbeat stop (which I ran after manually unmounting the shared filesystem for an fsck).

Suddenly I know it’s time for my yearly rant about this always surprising, never deterministic attempt at clustering.

serverA:~ # /etc/init.d/heartbeat start
Starting High-Availability services:
2011/10/06_18:24:30 INFO:  Running OK
2011/10/06_18:24:30 CRITICAL: Resource 172.x.y.z is active, and should not be!
2011/10/06_18:24:30 CRITICAL: Non-idle resources can affect data integrity!
2011/10/06_18:24:30 info: If you don't know what this means, then get help!
2011/10/06_18:24:30 info: Read the docs and/or source to /usr/share/heartbeat/ResourceManager for more details.
CRITICAL: Resource 172.x.y.z is active, and should not be!
CRITICAL: Non-idle resources can affect data integrity!
info: If you don't know what this means, then get help!
info: Read the docs and/or the source to /usr/share/heartbeat/ResourceManager for more details.
2011/10/06_18:24:30 CRITICAL: Non-idle resources will affect resource takeback!
2011/10/06_18:24:30 CRITICAL: Non-idle resources may affect data integrity!

I think it should read

If you're writing cluster software and don't know how to bring down ressources, then get help.

Of course, this is all history

Heartbeat as a software is deprecated these days, and even before that the “OCF” community had added a few more maintainers instead of just one.

(but *cough* we’re still using it – upgrading to fullblown corosync / pacemaker cluster is a very far jump and only jumping to the V2 mode of heartbeat/CRM is not far enough (since it used to be just as broken and crappy as the V1)

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s