You're mixing things up pretty thoroughly <G>.... SolrCloud with leaders and replicas is orthogonal to Master/Slave setups, generally people use one or the other. Master/Slave setups don't get NRT updates at all. I'm a little surprised that your setup works, it sounds like you have replication set up but then send update individually to the slaves, then rely on updating to the master to overwrite the full index on the slave? If this is what you're doing you should stop it <G>. It's _really_ dangerous to send updates to slaves in a master/slave situation, at some point the slave will think it's ahead of the master and will stop replicating and be out of sync.
So, you really have to choose one or the other and go with that. If you require NRT, set up SolrCloud and don't worry about it. All updates go to all nodes and they all get the soft commit... Best Erick On Fri, Jun 14, 2013 at 11:11 AM, Giovanni Bricconi <giovanni.bricc...@banzai.it> wrote: > I have recently upgraded our application from solr 3.6 to solr 4.2.1, and I > have just started learning about soft commits and partial updates. > > Currently I have one indexing node and 3 replicas of the same core, and > every modification goes through a dih delta index. This is usually ok but I > have some special cases where updates should be made visible very quickly. > > As I have seen with my first tests - it is possible to send partial updates > and soft commits to each replica and to the indexer - and when the indexer > gets an hard commit every replica is realligned. > > Is this the right approach or am I misunderstanding how to use this > feature? > > I don't see soft commit propagation to replicas when sending update to the > indexer only: is this true or maybe I haven't changed some configuration > files when porting the application to solr4? > > Giovanni
