The ReplicationHandler is not enforced as a singleton , but for all practical purposes it is a singleton for one core.
If an instance (a slice as you say) is setup as a repeater, It can act as both a master and slave in the repeater the configuration should be as follows MASTER |_____________SLAVE (I am a slave of MASTER) | REPEATER (I am a slave of MASTER and master to my slaves ) | | REPEATER_SLAVE( of REPEATER) the point is that REPEATER will have a slave section has a masterUrl which points to master and REPEATER_SLAVE will have a slave section which has a masterurl pointing to repeater On Wed, Aug 26, 2009 at 12:40 AM, J G<skinny_joe...@hotmail.com> wrote: > > Hello, > > We are running multiple slices in our environment. I have enabled JMX and I > am inspecting the replication handler mbean to obtain some information about > the master/slave configuration for replication. Is the replication handler > mbean a singleton? I only see one mbean for the entire server and it's > picking an arbitrary slice to report on. So I'm curious if every slice gets > its own replication handler mbean? This is important because I have no way of > knowing in this specific server any information about the other slices, in > particular, information about the master/slave value for the other slices. > > Reading through the Solr 1.4 replication strategy, I saw that a slice can be > configured to be a master and a slave, i.e. a repeater. I'm wondering how > repeaters work because let's say I have a slice named 'A' and the master is > on server 1 and the slave is on server 2 then how are these two servers > communicating to replicate? Looking at the jmx information I have in the > MBean both the isSlave and isMaster is set to true for my repeater so how > does this solr slice know if it's the master or slave? I'm a bit confused. > > Thanks. > > > > > _________________________________________________________________ > With Windows Live, you can organize, edit, and share your photos. > http://www.windowslive.com/Desktop/PhotoGallery -- ----------------------------------------------------- Noble Paul | Principal Engineer| AOL | http://aol.com
