08-20-2010
How to failover the cluster ?
How to failover the cluster ? GNU/Linux
By which command,
My Linux version
2008 x86_64 x86_64 x86_64 GNU/Linux
What are the prerequisites we need to take while failover ?
if any
Regards
10 More Discussions You Might Find Interesting
1. High Performance Computing
I have rcently setup a 4 node cluster running sun cluster 3.2
and I have installed 4 zones on each node. when installing the zones I had to install the zone on all nodes the on the last node do a zlogin -C <zonename>
this worked ok.
theni I tried to siwitch the zone to node a thei work... (14 Replies)
Discussion started by: lesliek
14 Replies
2. High Performance Computing
Provides a description of how to set up a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris.
More... (0 Replies)
Discussion started by: Linux Bot
0 Replies
3. HP-UX
I have a 2-node ServiceGuard cluster. One of the cluster packages has a volume group assigned to it. When I fail the package over to the other node, the volume group does not come up automatically on the other node.
I have to manually do a "vgchange -a y vgname" on the node before the package... (5 Replies)
Discussion started by: Wotan31
5 Replies
4. High Performance Computing
Dear All,
Can anyone explain about Pros and Cons of SUN and Veritas Cluster ?
Any comparison chart is highly appreciated.
Regards,
RAA (4 Replies)
Discussion started by: RAA
4 Replies
5. High Performance Computing
I have just completed a first RTFM of "Veritas Cluster Server Management Console Implementation Guide" 5.1, with a view to assessing it to possibly make our working lives easier.
Unfortunately, at my organisation, getting a test installation would be worse than pulling teeth, so I can't just go... (2 Replies)
Discussion started by: Beast Of Bodmin
2 Replies
6. Solaris
Hi,
We have two sun SPARC server in Clustered (Sun Cluster 3.1). For some reason, System 1 failed over to System 2. Where can I find the logs which could tell me the reason for this failover?
Thanks (5 Replies)
Discussion started by: Mack1982
5 Replies
7. Solaris
Yesterday my customer told me to expect a vcs upgrade to happen in the future. He also plans to stop using HDS and move to EMC.
Am thinking how to migrate to sun cluster setup instead.
My plan as follows leave the existing vcs intact as a fallback plan.
Then install and build suncluster on... (5 Replies)
Discussion started by: sparcguy
5 Replies
8. Solaris
Hello experts -
I am planning to install a Sun cluster 4.0 zone cluster fail-over. few basic doubts.
(1) Where should i install the cluster s/w binaries ?. ( global zone or the container zone where i am planning to install the zone fail-over)
(2) Or should i perform the installation on... (0 Replies)
Discussion started by: NVA
0 Replies
9. Solaris
Dear Experts,
If there is a possible Solaris Cluster failover to second node based on scan rate?
I need the documentation If solaris cluster can do this.
Thank You in Advance
Edy (3 Replies)
Discussion started by: edydsuranta
3 Replies
10. Red Hat
Hi Guys,
I am not much aware of clusters but i have few questions can someone provide the overview as it would be very helpful for me.
How can i perform cluster failover test to see all the services are failing back to other node ? If it is using veritas cluster then what kind of... (2 Replies)
Discussion started by: munna529
2 Replies
LEARN ABOUT SUSE
crm_failcount
CRM_FAILCOUNT(8) [FIXME: manual] CRM_FAILCOUNT(8)
NAME
crm_failcount - manipulate the failcount attribute on a given resource
SYNOPSIS
crm_failcount [-?|-V] -D -u|-U node -r resource
crm_failcount [-?|-V] -G -u|-U node -r resource
crm_failcount [-?|-V] -v string -u|-U node -r resource
DESCRIPTION
Heartbeat implements a sophisticated method to compute and force failover of a resource to another node in case that resource tends to fail
on the current node. A resource carries a resource_stickiness attribute to determine how much it prefers to run on a certain node. It also
carries a resource_failure_stickiness that determines the threshold at which the resource should failover to another node.
The failcount attribute is added to the resource and increased on resource monitoring failure. The value of failcount multiplied by the
value of resource_failure_stickiness determines the failover score of this resource. If this number exceeds the preference set for this
resource, the resource is moved to another node and not run again on the original node until the failure count is reset.
The crm_failcount command queries the number of failures per resource on a given node. This tool can also be used to reset the failcount,
allowing the resource to run again on nodes where it had failed too often.
OPTIONS
--help, -?
Print a help message.
--verbose, -V
Turn on debug information.
Note
Increase the level of verbosity by providing additional instances.
--quiet, -Q
When doing an attribute query using -G, print just the value to stdout. Use this option with -G.
--get-value, -G
Retrieve rather than set the preference.
--delete-attr, -D
Specify the attribute to delete.
--attr-value string, -v string
Specify the value to use. This option is ignored when used with -G.
--node-uuid node_uuid, -u node_uuid
Specify the UUID of the node to change.
--node-uname node_uname, -U node_uname
Specify the uname of the node to change.
--resource-id resource name, -r resource name
Specify the name of the resource on which to operate.
EXAMPLES
Reset the failcount for the resource myrsc on the node node1:
crm_failcount -D -U node1 -r my_rsc
Query the current failcount for the resource myrsc on the node node1:
crm_failcount -G -U node1 -r my_rsc
FILES
/var/lib/heartbeat/crm/cib.xml--the CIB (minus status section) on disk. Editing this file directly is strongly discouraged.
SEE ALSO
???, ???, and the Linux High Availability FAQ Web site[1]
AUTHOR
crm_failcount was written by Andrew Beekhof.
NOTES
1. Linux High Availability FAQ Web site
http://www.linux-ha.org/v2/faq/forced_failover
[FIXME: source] 07/05/2010 CRM_FAILCOUNT(8)