Are you absolutely and totally sure that the <uniqueKey> s are unique (id by default) when you say that the only difference is the date? It sounds like you're somehow getting the same doc indexed with two (or more) different IDs.
You can look at this by identifying some suspect IDs and issuing queries like solr/collection1_shard1_replica1?q=id:suspect_id&distrib=false against a single replica for each shard. The doc shoule be found on one and only one shard (any replica). It's important that you add &distrib=false and address a specific replica when you do this. Best, Erick On Thu, Dec 1, 2016 at 11:42 AM, Halim Chaibi <halim.cha...@gmail.com> wrote: > Hi, > We are using solr cloud 4.10.4, with 4 shards, one replica for each shard. > The id field definition is a unique composite key id (key_id!document_id) > <field name="id" type="string" indexed="true" stored="true" required="true" > /> > > We are having an issue with the pagination: > Some documents found with a request, let's says, of 100 documents starting > from 200(rows=100&start=200) > Are still found with the same request with rows=100&start=300. > The only difference with the same document found with the two request is in > the timestamp, it's very slight difference a few ms. > > Please, can you help us to figure out what is happening ? > thank you > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Pagination-issue-tp4308226.html > Sent from the Solr - User mailing list archive at Nabble.com.