Visit Our UNIX and Linux User Community

Special Forums UNIX Desktop Questions & Answers How can I replicate master master and master master MySQL databse replication and HA? Post 302901678 by Palak Sharma on Thursday 15th of May 2014 01:15:26 AM
Old 05-15-2014
Question How can I replicate master master and master master MySQL databse replication and HA?

I have an application desigend in PHP and MySQl running on apache web server that I is running on a Amazon EC2 server Centos. I want to implement the master-master and master slave replication and high availability disaster recovery on this application database.

For this I have created two servers and have installed the same application and database on both the servers.

I want to achieve something like this:


1. If the user updates (insert,delete,modify) any record on any server then the same should be replicated on the other server.

2. If one of the server goes down the other should be able to serve the request.


Kindly help me to achieve the same.
 

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Master Console

I was a sys admin on a HP3000. I was able to virtually move the console where ever I needed it for commands that had to be done at the master console. So I could be at home and perform some functions that you would usually have to do from the console. Now I am sys admin newbee on an AIX pseries.... (2 Replies)
Discussion started by: Beetlejuice
2 Replies

2. AIX

nim master

Hi, I want to know what are steps required to create nim master in aix? Regards, Manoj (1 Reply)
Discussion started by: manoj.solaris
1 Replies

3. AIX

nim master

Hi, I want to know how to create nim master in AIX 5.3. Regards, Manoj (0 Replies)
Discussion started by: manoj.solaris
0 Replies

4. Web Development

MySQL Master-Slave Configuration: Don't Replicate a Row of a Table?

Anyone have a clue about this? I have checked the MySQL documentation and it does not seem possible to exclude a row of a table from replication between Master and Slave. It seems that replication in MySQL can only be managed at the table level, not at the row level. Does anyone know a work... (5 Replies)
Discussion started by: Neo
5 Replies

5. Red Hat

Master logs for all the operations performed on mysql DB

is there any such thing as master logs for all the operations performed on mysql database. thing is i need to find the operations performed on mysql on a linux server running on RHEL 5.7 for the past 2 days. One more thing i found out that the bin logs will be refreshed whenever server goes to... (2 Replies)
Discussion started by: vivek d r
2 Replies
IPROP(8)						    BSD System Manager's Manual 						  IPROP(8)

NAME
iprop, ipropd-master, ipropd-slave -- propagate changes to a Heimdal Kerberos master KDC to slave KDCs SYNOPSIS
ipropd-master [-c string | --config-file=string] [-r string | --realm=string] [-k kspec | --keytab=kspec] [-d file | --database=file] [--slave-stats-file=file] [--time-missing=time] [--time-gone=time] [--detach] [--version] [--help] ipropd-slave [-c string | --config-file=string] [-r string | --realm=string] [-k kspec | --keytab=kspec] [--time-lost=time] [--detach] [--version] [--help] master DESCRIPTION
ipropd-master is used to propagate changes to a Heimdal Kerberos database from the master Kerberos server on which it runs to slave Kerberos servers running ipropd-slave. The slaves are specified by the contents of the slaves file in the KDC's database directory, e.g. /var/heimdal/slaves. This has principals one per-line of the form iprop/slave@REALM where slave is the hostname of the slave server in the given REALM, e.g. iprop/kerberos-1.example.com@EXAMPLE.COM On a slave, the argument master specifies the hostname of the master server from which to receive updates. In contrast to hprop(8), which sends the whole database to the slaves regularly, iprop normally sends only the changes as they happen on the master. The master keeps track of all the changes by assigning a version number to every change to the database. The slaves know which was the latest version they saw, and in this way it can be determined if they are in sync or not. A log of all the changes is kept on the mas- ter. When a slave is at an older version than the oldest one in the log, the whole database has to be sent. The changes are propagated over a secure channel (on port 2121 by default). This should normally be defined as ``iprop/tcp'' in /etc/services or another source of the services database. The master and slaves must each have access to a keytab with keys for the iprop service principal on the local host. There is a keep-alive feature logged in the master's slave-stats file (e.g. /var/heimdal/slave-stats). Supported options for ipropd-master: -c string, --config-file=string -r string, --realm=string -k kspec, --keytab=kspec keytab to get authentication from -d file, --database=file Database (default per KDC) --slave-stats-file=file file for slave status information --time-missing=time time before slave is polled for presence (default 2 min) --time-gone=time time of inactivity after which a slave is considered gone (default 5 min) --detach detach from console --version --help Supported options for ipropd-slave: -c string, --config-file=string -r string, --realm=string -k kspec, --keytab=kspec keytab to get authentication from --time-lost=time time before server is considered lost (default 5 min) --detach detach from console --version --help Time arguments for the relevant options above may be specified in forms like 5 min, 300 s, or simply a number of seconds. FILES
slaves, slave-stats in the database directory. SEE ALSO
krb5.conf(5), hprop(8), hpropd(8), iprop-log(8), kdc(8). BSD
May 24, 2005 BSD

Featured Tech Videos

All times are GMT -4. The time now is 10:17 AM.
Unix & Linux Forums Content Copyright 1993-2021. All Rights Reserved.
Privacy Policy