Ok, so our issue sounds like a combination of not having softCommits properly done, combined with SOLR-4260.
Thanks everyone! On 01/24/2014 11:04 PM, Erick Erickson wrote:
Right. There updates are guaranteed to be on the replicas and in their transaction logs. That doesn't mean they're searchable, however. For a document to be found in a search there must be a commit, either soft, or hard with openSearcher=true. Here's a post that outlines all this. If you have discrepancies when after commits, that's a problem.... Best, Erick On Fri, Jan 24, 2014 at 8:52 PM, Nathan Neulinger <nn...@neulinger.org> wrote: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
-- ------------------------------------------------------------ Nathan Neulinger nn...@neulinger.org Neulinger Consulting (573) 612-1412
