Sponsored Content
Top Forums Web Development MySQL DevZone RSS Does Failover/SwitchOver mechanisam supported in MySQL? Post 302375242 by amit_27 on Friday 27th of November 2009 04:54:11 AM
Old 11-27-2009
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?


Any help on this highly appreciated.



Regards,
Amit
 

7 More Discussions You Might Find Interesting

1. Solaris

Interfaces do not failover

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)
Discussion started by: StorageGuy
5 Replies

2. Solaris

Cluster 2.2 Switchover Oftenly

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)
Discussion started by: madanrajan
1 Replies

3. UNIX for Advanced & Expert Users

directories failover

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)
Discussion started by: prvnrk
3 Replies

4. AIX

failover on 4.5 hacmp

Hi All, How do I trigger the failover on the second hacmp server? Please give me idea and I will do the rest. Thanks, itik (2 Replies)
Discussion started by: itik
2 Replies

5. Solaris

EMC Failover

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)
Discussion started by: glenioborges
4 Replies

6. IP Networking

IP failover needed

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)
Discussion started by: markdjones82
4 Replies

7. Gentoo

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 (3 Replies)
Discussion started by: sidharthmellam
3 Replies
tels(7) 						 Miscellaneous Information Manual						   tels(7)

NAME
tels, telm - STREAMS Telnet slave (pseudo-terminal) driver, STREAMS Telnet master driver (used by telnetd only), respectively SYNOPSIS
DESCRIPTION
A Telnet pseudo-terminal consists of a tightly-coupled pair of character devices, called the master device and slave device. The master and slave device drivers work together to provide a Telnet connection on the server side where the master provides a connection to and the slave provides a terminal device special file access for the Telnet application processes, as depicted below: -------------------------- | Pseudo terminal functions| Application <--> |--------------------------| <--> telnetd Processes | Slave | Master | | (tels) | (telm) | -------------------------- The slave driver, with (STREAMS pty emulation module) and (STREAMS line discipline module) pushed on top (not shown for simplicity), pro- vides a terminal interface as described in termio(7). Whereas devices that provide the terminal interface described in termio(7) have a hardware device behind them; in contrast, the slave device has manipulating it through the master side of the Telnet pseudo terminal. There are no nodes in the file system for each individual master device. Rather, the master driver is set up as a STREAMS clone(7) driver with its major device number set to the major for the clone driver and its minor device number set to the major for the driver. The master driver is opened by telnetd using the open(2) system call with as the device file parameter. The clone open finds the next available minor number for the master device. The master device is available only if it and its corresponding slave device are not already opened. In order to use the STREAMS Telnet subsystem, a node for the master driver and N number of Telnet slave devices must be installed. The number of slave devices is set by a kernel tunable parameter called This can be modified using SAM; its default and minimum value is 60. The value of is the upper limit of the number of telnet sessions that can be opened. Multiple opens are allowed on the Telnet slave device. The master and slave drivers pass all STREAMS messages to their adjacent drivers. When the connection is closed from the Telnet client side, an message is sent to the corresponding slave device which will render that slave device unusable. The process on the slave side gets the errno when attempting a write(2) system call to the slave device file but it will be able to read any data remaining in the slave stream. Finally, when all the data has been read, the read(2) system call will return 0, indicating that the slave can no longer be used. AUTHOR
and were developed by HP. FILES
Streams Telnet master clone device Streams slave devices where N is the minor number of the slave device and 0 < N < SEE ALSO
insf(1M), open(2), ioctl(2), streamio(7), ldterm(7), telnetd(1M), ptem(7). tels(7)
All times are GMT -4. The time now is 02:39 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy