bq: If I understood you correctly - this means the update section of the admin should be avoided when using a sharded install, because it doesn't guarantee a given document ID will be sent to the same shard as the previous version of the same document?
You've got it, but.... I want to emphasize that I'm _speculating_ here based on the fact that the admin pages originated in non-solr-cloud days and are fairly cloud-ignorant. Someone would have to, I think, do something special to make indexing via the admin UI cloud-aware. So my scenario seems at least plausible... Hmmm, this is worth a JIRA though, I've raised one. P.S. There's the bare start of an umbrella project of things to do for a SolrCloud-aware admin UI here: https://issues.apache.org/jira/browse/SOLR-6082 Best, Erick On Mon, Jun 23, 2014 at 12:42 AM, yann <yannick.lallem...@gmail.com> wrote: > Hi Erik, > > thanks for your answer. I didn't manually assign docs to shards, I indexed > all docs on one server, which then assigned it to shards (based on the > default Solr behaviour, based on the document ID I believe). > > If I understood you correctly - this means the update section of the admin > should be avoided when using a sharded install, because it doesn't guarantee > a given document ID will be sent to the same shard as the previous version > of the same document? > > Thanks > > Yann > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Solr-alternates-returning-different-versions-of-the-same-document-tp4143006p4143375.html > Sent from the Solr - User mailing list archive at Nabble.com.
