A
A
Alexey Yamschikov2016-01-21 14:59:16
linux
Alexey Yamschikov, 2016-01-21 14:59:16

RHCS: When the node on which the active service is running fails, it does not migrate to the remaining node, how to configure?

There are 2 nodes. A cluster based on RedHat Cluster Suite was made of them
. The task is to switch the service to the second one when the active node crashes. By service, I mean a script that switches the failoverip address from the provider to the node on which it is running. It was not possible to make the standard ip_address resource, because you need to switch ipaddress through the provider's API.
Done, it started. I look at the logs - everything is buzzing.
I turn off the master node (this is a VPS - I do a hard shutdown). On the second node, the logs show that the first node is down. But no action is taken to switch the service to the remaining one.
If the first node goes up, then the service remains there.
If I disable the normal Shutdown, then the service moves to the second node itself.
The service is hung on a service group of these two nodes.
The properties of the service are:

Service Name	<b>servgr1</b>
Automatically Start This Service	<b>+</b>
Run Exclusive	<b>-</b>
Failover Domain <b>FODOM1</b>	
Recovery Policy	<b>relocate</b>

FailoverDomain setup:
-	Prioritized	Order the nodes to which services failover.
+	Restricted	Service can run only on nodes specified.
+	No Failback	Do not send service back to 1st priority node when it becomes available again.

With both nodes up, I can manually switch the service to another node.
How to do automatic switching? CHADNT?

Answer the question

In order to leave comments, you need to log in

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question