search

chusiang / mysql-master-master

Automatically exported from code.google.com/p/mysql-master-master
GNU General Public License v2.0
1 stars 1 forks source link

move_role sets server to slave of self if mmmd_agent isn't running #7

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Kill mmmd_agent on the reader of the monitored servers.
2. switch the writer role to that server.
3. switch the writer role back away from that server.

What is the expected output? What do you see instead?

I think if the agent on the server can't be contacted, MMM should complain
and refuse to go ahead.  Instead it moves the writer role, but when it
tries to move it back, it complains (though it still seems to move it back,
actually) and then somehow the server ends up being set as a slave of
itself.  Then the server goes into REPLICATION_FAIL state.

Original issue reported on code.google.com by baron.schwartz on 16 Jun 2008 at 4:36

GoogleCodeExporter commented 9 years ago 
I can't reproduce the problem:

  db1(10.20.30.31): master/ONLINE. Roles: reader(10.20.30.52;), writer(10.20.30.50;)
  db2(10.20.30.32): master/ONLINE. Roles: reader(10.20.30.53;)
  db3(10.20.30.33): slave/ONLINE. Roles: reader(10.20.30.51;)

on db2: kill `cat $MMMD_AGENT_PIDFILE`
on mon: mmm_control move_role writer db2
Command sent to monitoring host. Result: ERROR: Can't reach agent daemon on 
'db2'!
Can't move roles there!

Original comment by m...@pascalhofmann.de on 2 Nov 2008 at 6:25

GoogleCodeExporter commented 9 years ago

Original comment by baron.schwartz on 15 Jan 2009 at 2:05