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.
 
Test Your Knowledge in Computers #71
Difficulty: Easy
Linux, macOS, Android, iOS, Chrome OS, Orbis OS used on the PlayStation 4, whatever firmware is running on your router, all of these operating systems are generally referred to as a Unix-like operating system.
True or False?

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
OCF_HEARTBEAT_MYSQL(7)						OCF resource agents					    OCF_HEARTBEAT_MYSQL(7)

NAME
ocf_heartbeat_mysql - Manages a MySQL database instance SYNOPSIS
mysql [start | stop | status | monitor | promote | demote | meta-data | validate-all] DESCRIPTION
Resource script for MySQL. May manage a standalone MySQL database, a clone set with externally managed replication, or a complete master/slave replication setup. SUPPORTED PARAMETERS
binary Location of the MySQL server binary (optional, string, default /usr/bin/mysqld_safe) client_binary Location of the MySQL client binary (optional, string, default mysql) config Configuration file (optional, string, default /etc/mysql/my.cnf) datadir Directory containing databases (optional, string, default /var/lib/mysql) user User running MySQL daemon (optional, string, default mysql) group Group running MySQL daemon (for logfile and directory permissions) (optional, string, default mysql) log The logfile to be used for mysqld. (optional, string, default /var/log/mysql.log) pid The pidfile to be used for mysqld. (optional, string, default /var/run/mysqld/mysqld.pid) socket The socket to be used for mysqld. (optional, string, default /var/lib/mysqld/mysqld.sock) test_table Table to be tested in monitor statement (in database.table notation) (optional, string, default mysql.user) test_user MySQL test user (optional, string, default root) test_passwd MySQL test user password (optional, string, no default) enable_creation If the MySQL database does not exist, it will be created (optional, integer, default 0) additional_parameters Additional parameters which are passed to the mysqld on startup. (e.g. --skip-external-locking or --skip-grant-tables) (optional, string, no default) replication_user MySQL replication user. This user is used for starting and stopping MySQL replication, for setting and resetting the master host, and for setting and unsetting read-only mode. Because of that, this user must have SUPER, REPLICATION SLAVE, REPLICATION CLIENT, and PROCESS privileges on all nodes within the cluster. (optional, string, no default) replication_passwd MySQL replication password. Used for replication client and slave. (optional, string, no default) replication_port The port on which the Master MySQL instance is listening. (optional, string, default 3306) max_slave_lag The maximum number of seconds a replication slave is allowed to lag behind its master. Do not set this to zero. What the cluster manager does in case a slave exceeds this maximum lag is determined by the evict_outdated_slaves parameter. (optional, integer, default 3600) evict_outdated_slaves If set to true, any slave which is more than max_slave_lag seconds behind the master has its MySQL instance shut down. If this parameter is set to false in a primitive or clone resource, it is simply ignored. If set to false in a master/slave resource, then exceeding the maximum slave lag will merely push down the master preference so the lagging slave is never promoted to the new master. (optional, boolean, default false) SUPPORTED ACTIONS
This resource agent supports the following actions (operations): start Starts the resource. Suggested minimum timeout: 120. stop Stops the resource. Suggested minimum timeout: 120. status Performs a status check. Suggested minimum timeout: 60. monitor Performs a detailed status check. Suggested minimum timeout: 30. Suggested interval: 20. monitor (Master role) Performs a detailed status check. Suggested minimum timeout: 30. Suggested interval: 10. monitor (Slave role) Performs a detailed status check. Suggested minimum timeout: 30. Suggested interval: 30. promote Promotes the resource to the Master role. Suggested minimum timeout: 120. demote Demotes the resource to the Slave role. Suggested minimum timeout: 120. notify Suggested minimum timeout: 90. validate-all Performs a validation of the resource configuration. Suggested minimum timeout: 5. meta-data Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5. EXAMPLE
The following is an example configuration for a mysql resource using the crm(8) shell: primitive p_mysql ocf:heartbeat:mysql op monitor depth="0" timeout="30" interval="20" op monitor role="Master" depth="0" timeout="30" interval="10" op monitor role="Slave" depth="0" timeout="30" interval="30" ms ms_mysql p_mysql meta notify="true" interleave="true" SEE ALSO
http://www.linux-ha.org/wiki/mysql_(resource_agent) AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors) resource-agents UNKNOWN 03/09/2014 OCF_HEARTBEAT_MYSQL(7)

Featured Tech Videos

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