What steps will reproduce the problem?
1. set replication in a fan-in topology, with at least two slave services and
one master service in the current host.
2. modify one of the slave services to allow bi-directional unsafe statements.
./tungsten/configure-service -U --allow-bidi-unsafe=true alpha
3. restart the replicator
4. Check the status. The role has changed from slave to master
What is the expected output?
NAME VALUE
---- -----
appliedLastSeqno: 5
appliedLatency : 0.0020
role : slave
serviceName : alpha
serviceType : remote
started : true
state : ONLINE
What do you see instead?
NAME VALUE
---- -----
appliedLastSeqno: 5
appliedLatency : 0.0020
role : master
serviceName : alpha
serviceType : remote
started : true
state : ONLINE
What is the possible cause?
N/A
What is the proposed solution?
configure-service should only modify what is requested
Original issue reported on code.google.com by g.maxia on 1 Jul 2011 at 9:33
Original issue reported on code.google.com by
g.maxia
on 1 Jul 2011 at 9:33