@Mark Miller Please help~ On Tue, Oct 11, 2016 at 5:32 PM, Jerome Yang <jey...@pivotal.io> wrote:
> Using curl do some tests. > > curl 'http://localhost:8983/solr/restore_test_collection/update? > *commit=true*&wt=json' --data-binary @test.json -H > 'Content-type:application/json' > > The leader don't have new documents, but other replicas have. > > curl 'http://localhost:8983/solr/restore_test_collection/update? > *commitWithin**=1000*&wt=json' --data-binary @test.json -H > 'Content-type:application/json' > All replicas in shard1 have new documents include leader, and all new > documents route to shard1. > > On Tue, Oct 11, 2016 at 5:27 PM, Jerome Yang <jey...@pivotal.io> wrote: > >> Hi all, >> >> I'm facing a strange problem. >> >> Here's a solrcloud on a single machine which has 2 solr nodes, version: >> solr6.1. >> >> I create a collection with 2 shards and replica factor is 3 with default >> router called "test_collection". >> Index some documents and commit. Then I backup this collection. >> After that, I restore from the backup and name the restored collection >> "restore_test_collection". >> Query from "restore_test_collection". It works fine and data is >> consistent. >> >> Then, I index some new documents, and commit. >> I find that the documents are all indexed in shard1 and the leader of >> shard1 don't have these new documents but other replicas do have these new >> documents. >> >> Anyone have this issue? >> Really need your help. >> >> Regards, >> Jerome >> > >
