1. Indexing 100-200 docs per second. 2. Doing Pkill -9 java to 2 replicas (not the leader) in shard 3 (while indexing). 3. Indexing for 10-20 minutes and doing hard commit. 4. Doing Pkill -9 java to the leader and then starting one replica in shard 3 (while indexing).
I think you're in uncharted territory. By only having the leader running, indexing docs to it, then killing it, there's no way for one of the restarted followers to know what docs were indexed. Eventually the follower will become the leader and the docs are just lost. Updates are NOT stored on ZK for instance. Why do you expect the machines to "stay in down status"? SolrCloud is doing the best it can. How do you expect this scenario to recover? FWIW, Erick On Thu, May 8, 2014 at 8:00 AM, adfel70 <adfe...@gmail.com> wrote: > Solr & Collection Info: > solr 4.8 , 4 shards, 3 replicas per shard, 30-40 milion docs per shard. > > Process: > 1. Indexing 100-200 docs per second. > 2. Doing Pkill -9 java to 2 replicas (not the leader) in shard 3 (while > indexing). > 3. Indexing for 10-20 minutes and doing hard commit. > 4. Doing Pkill -9 java to the leader and then starting one replica in shard > 3 (while indexing). > 5. After 20 minutes starting another replica in shard 3 ,while indexing (not > the leader in step 1). > > Results: > 2. Only the leader is active in shard 3. > 3. Thousands of docs were added to the leader in shard 3. > 4. After staring the replica, it's state was down and after 10 minutes it > became the leader in cluster state (and still down). no servers hosting > shards for index and search requests. > 5. After starting another replica, it's state was recovering for 2-3 minutes > and then it became active (not leader in cluster state). > 6. Index, commit and search requests are handeled in the other replicae > (*active status, not leader!!!*). > > > Expected: > 5. To stay in down status. > *6. Not to handel index, commit and search requests - no servers hosting > shards!* > > Thanks! > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Replica-as-a-leader-tp4135077.html > Sent from the Solr - User mailing list archive at Nabble.com.
