Skip to main content

Configure Master / Slave Replication MySQL XAMPP

Mysql Master Server Configuration
First Lets go to Replication panel on XAMPP.
Screenshot at 2012-04-24 02_13_51
Next Select Configure as Master
Screenshot at 2012-04-24 02_14_03
You can configure Replication as ALL or Selective. I have done selective where I select few DBs to Replicate.
Once you are done you need to add the lines below in the my.cnf file.
# ***** Added Lines here ****
server-id=4745869
log-bin=mysql-bin
log-error=mysql-bin.err
binlog_do_db=saggezza_cats,saggezza_catstesting
# ***** Till Here ****
Here are Ignoring all the DBs for Replication except the two above.
Screenshot at 2012-04-24 02_21_40
Go to /opt/lampp/etc/my.cnf

Screenshot at 2012-04-24 02_22_11
Added the lines as I mentioned above above. Also Make sure “max_allowed_packet = 16M”

Screenshot at 2012-04-24 02_23_07
Screenshot at 2012-04-24 02_23_16
Make sure to comment out he existing server-id as we have already given above.
Screenshot at 2012-04-24 02_23_39
Restart XAMPP
$ sudo ./opt/lampp/lampp restart
Screenshot at 2012-04-24 02_24_02
Once you restart XAMPP, you can see that Mysql Server is started as Master.
Screenshot at 2012-04-24 02_24_15
Next Lets Create a Replication user and give it privileges as the slave needs this information to connect to the Master.
Screenshot at 2012-04-24 02_24_40
I have given root but you can give any username you want.
Screenshot at 2012-04-24 02_25_13

MySQL Slave Configuration 
First lets add Server-id to our slave as mentioned.
server-id=9384593
Screenshot at 2012-04-24 02_28_29
Screenshot at 2012-04-24 02_29_29
Now lets connect to Master.
Screenshot at 2012-04-24 02_30_08
You will get a confirmation about he successful connection to Master.
Screenshot at 2012-04-24 02_30_20
Now we need to start SLAVE I/O and Sql Threads.
Screenshot at 2012-04-24 02_31_07
They are right under “Control Slave” as below
Screenshot at 2012-04-24 02_31_28
Now you can see the threads running.
NOTE: If you face any issues getting the threads started then please check logs. In my case IO Thread was not starting. When I checked the log I found that I had two server-id’s in the my.cnf file. Also sometimes you will get IO error due to max_allowed_packet as well, as this is by default set to 1MB, which needs to be around 16MB.
/opt/lampp/var/mysql/mysql-bin
Screenshot at 2012-04-24 02_31_37
Now we can see all the DBs in Replication Mode. Now any Updates to Master will reflect on the slave.
Screenshot at 2012-04-24 03_24_28
This will have the MASTER-SLAVE for Mysql Server is Ready.
Enjoy.

Comments

Popular posts from this blog

Cloudera Manager - Duplicate entry 'zookeeper' for key 'NAME'.

We had recently built a cluster using cloudera API’s and had all the services running on it with Kerberos enabled. Next we had a requirement to add another kafka cluster to our already exsisting cluster in cloudera manager. Since it is a quick task to get the zookeeper and kafka up and running. We decided to get this done using the cloudera manager instead of the API’s. But we faced the Duplicate entry 'zookeeper' for key 'NAME' issue as described in the bug below. https://issues.cloudera.org/browse/DISTRO-790 I have set up two clusters that share a Cloudera Manger. The first I set up with the API and created the services with capital letter names, e.g., ZOOKEEPER, HDFS, HIVE. Now, I add the second cluster using the Wizard. Add Cluster->Select Hosts->Distribute Parcels->Select base HDFS Cluster install On the next page i get SQL errros telling that the services i want to add already exist. I suspect that the check for existing service names does n

Zabbix History Table Clean Up

Zabbix history table gets really big, and if you are in a situation where you want to clean it up. Then we can do so, using the below steps. Stop zabbix server. Take table backup - just in case. Create a temporary table. Update the temporary table with data required, upto a specific date using epoch . Move old table to a different table name. Move updated (new temporary) table to original table which needs to be cleaned-up. Drop the old table. (Optional) Restart Zabbix Since this is not offical procedure, but it has worked for me so use it at your own risk. Here is another post which will help is reducing the size of history tables - http://zabbixzone.com/zabbix/history-and-trends/ Zabbix Version : Zabbix v2.4 Make sure MySql 5.1 is set with InnoDB as innodb_file_per_table=ON Step 1 Stop the Zabbix server sudo service zabbix-server stop Script. echo "------------------------------------------" echo " 1. Stopping Zabbix Server &quo

Access Filter in SSSD `ldap_access_filter` [SSSD Access denied / Permission denied ]

Access Filter Setup with SSSD ldap_access_filter (string) If using access_provider = ldap , this option is mandatory. It specifies an LDAP search filter criteria that must be met for the user to be granted access on this host. If access_provider = ldap and this option is not set, it will result in all users being denied access. Use access_provider = allow to change this default behaviour. Example: access_provider = ldap ldap_access_filter = memberOf=cn=allowed_user_groups,ou=Groups,dc=example,dc=com Prerequisites yum install sssd Single LDAP Group Under domain/default in /etc/sssd/sssd.conf add: access_provider = ldap ldap_access_filter = memberOf=cn=Group Name,ou=Groups,dc=example,dc=com Multiple LDAP Groups Under domain/default in /etc/sssd/sssd.conf add: access_provider = ldap ldap_access_filter = (|(memberOf=cn=System Adminstrators,ou=Groups,dc=example,dc=com)(memberOf=cn=Database Users,ou=Groups,dc=example,dc=com)) ldap_access_filter accepts standa