Does Failover/SwitchOver mechanisam supported in MySQL?
Hi,
I need setup like:
Consider, Master - A and Slave - B machine.
We do operations on master will replicate to Slave. But in case if
Case 1:
If master(A) goes down then changes / operations will be done on slave (B).
Case 2.
Later on , If slave down and Master is already up. Then changes on slave need to replicate on Master for consistency of data. and operations / changes will e done on Master.
Is MySQL database support this kind of mechanism? If Yes, How?
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 (3 Replies)
All,
I am looking to setup a simple IP failover setup, but it seems every place i look has some difficult setup like pacemaker or LVS.
I only want to handle the IP piece to failover a VIP.
Any suggestions? I checked out keepalived and that my work for me. (4 Replies)
Hi guys,
I'm running vxdmp and powerpath at the same time. Vxdmp for internal disks and powerpath for external.
The problem is that, on the failover tests which a fiber cable should be removed, the system cannot recognize the disks.
Any hints on how to configure powerpath in order to... (4 Replies)
Hi,
I have 3 directories (/1 /2 and /3) with same contents and want to achieve fail over among them.
The Solution i thought of:
1. link /data to /1 (and provide users with /data to access)
2. CRON a script (to run every minute) to verify if /1 exist or not, if it does not exist (or its... (3 Replies)
Hai,
I am having ultra machine where SUN o.s 5.6 is installed with Clusters 2.2. Here, i am facing a problem of Cluster switchover oftenly. Can you suggest a solution.
Madan (1 Reply)
Would anyone know why a V440 Solaris 9 machine's interfaces (ce0 and ce1)
will not failover?
Both interfaces are on the same subnet, but different IPs. I can pull the plug on once interface (ce0) and ce1 will be accessible. I can reverse it and pull ce1, and ce0 will NOT be accessible. ... (5 Replies)
OCF_HEARTBEAT_DRBD(7) OCF resource agents OCF_HEARTBEAT_DRBD(7)NAME
ocf_heartbeat_drbd - Manages a DRBD resource (deprecated)
SYNOPSIS
drbd [start | stop | monitor | promote | demote | meta-data | validate-all]
DESCRIPTION
Deprecation warning: This agent is deprecated and may be removed from a future release. See the ocf:linbit:drbd resource agent for a
supported alternative. -- This resource agent manages a Distributed Replicated Block Device (DRBD) object as a master/slave resource. DRBD
is a mechanism for replicating storage; please see the documentation for setup details.
SUPPORTED PARAMETERS
drbd_resource
The name of the drbd resource from the drbd.conf file. (unique, required, string, default drbd0)
drbdconf
Full path to the drbd.conf file. (optional, string, default /etc/drbd.conf)
clone_overrides_hostname
Whether or not to override the hostname with the clone number. This can be used to create floating peer configurations; drbd will be
told to use node_<cloneno> as the hostname instead of the real uname, which can then be used in drbd.conf. (optional, boolean, default
no)
ignore_deprecation
If set to true, suppresses the deprecation warning for this agent. (optional, boolean, default false)
SUPPORTED ACTIONS
This resource agent supports the following actions (operations):
start
Starts the resource. Suggested minimum timeout: 240.
promote
Promotes the resource to the Master role. Suggested minimum timeout: 90.
demote
Demotes the resource to the Slave role. Suggested minimum timeout: 90.
notify
Suggested minimum timeout: 90.
stop
Stops the resource. Suggested minimum timeout: 100.
monitor (Slave role)
Performs a detailed status check. Suggested minimum timeout: 20. Suggested interval: 20.
monitor (Master role)
Performs a detailed status check. Suggested minimum timeout: 20. Suggested interval: 10.
meta-data
Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5.
validate-all
Performs a validation of the resource configuration. Suggested minimum timeout: 30.
EXAMPLE
The following is an example configuration for a drbd resource using the crm(8) shell:
primitive p_drbd ocf:heartbeat:drbd
params
drbd_resource="drbd0"
op monitor depth="0" timeout="20" interval="20" role="Slave"
op monitor depth="0" timeout="20" interval="10" role="Master"
ms ms_drbd p_drbd
meta notify="true" interleave="true"
SEE ALSO
http://www.linux-ha.org/wiki/drbd_(resource_agent)
AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors)
resource-agents UNKNOWN 03/09/2014 OCF_HEARTBEAT_DRBD(7)
