WIP: Added option to prepare mysql servers for replication #94
Loading…
Reference in New Issue
No description provided.
Delete Branch "mysql_replication"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Doesnt start the replication, but prepares everything for it.
Hey :)
A quick question : Do we always want to install xinetd ?
For the check done via xinetd, wouldn't it be better to rely on the mysql check as used by nagios ? There's a simplier check that we use. It's documented on the public wiki on the HAProxy page that doesn't even write temporary files in /tmp
Also :
You don't need to set the check_mysql_slave check command as it's aleady defined here
I don't get how dbadmin.sh is related to replication.
@ -0,0 +50,4 @@
dest: '/usr/share/scripts/'
mode: '0755'
- name: 'Copy dbadmin script'
This is not related to replication.
I'm not sure it's the right place to put it
You're right. Is this script even necessary ? I think I can remove it completely.
@ -0,0 +1,3 @@
# ansible managed
command[check_mysql_slave]=/usr/lib/nagios/plugins/check_mysql --check-slave -H localhost -f ~nagios/.my.cnf -w 1800 -c 3600
Dumplicate with our default nrpe config
You're right, I'll remove it.
xinetd is for advanced haproxy check, it's always better for critical replication, but not necessary in somes cases.
This was based on a former client case. Does the simple nagios check make sure the database is synced ? Or does it only check if the database is up ? And do we want to keep the xinetd version as on option ?
Pull request closed