How can we issue an update request and be certain that all of the replicas in
the SolrCloud cluster are up to date?
I found this post:
http://comments.gmane.org/gmane.comp.jakarta.lucene.solr.user/79886
which seems to indicate that all replicas for a shard must finish/succeed before it returns to client that the operation
succeeded - but we've been seeing behavior lately (until we configured automatic soft commits) where the replicas were
almost always "not current" - i.e. the replicas were missing documents/etc.
Is this something wrong with our cloud setup/replication, or am I misinterpreting the way that updates in a cloud
deployment are supposed to function?
If it's a problem with our cloud setup, do you have any suggestions on
diagnostics?
Alternatively, are we perhaps just using it wrong?
-- Nathan
------------------------------------------------------------
Nathan Neulinger nn...@neulinger.org
Neulinger Consulting (573) 612-1412
