You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by adfel70 <ad...@gmail.com> on 2014/05/12 16:35:22 UTC

solr 4.8 Leader Problem

*Solr &Collection Info:*
Solr 4.8 , 4 shards, 3 replicas per shard, 30-40 million 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). 
6. After 10 minutes starting the rep that was 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). 
   Index, commit and search requests are handled in the other replica
(active status, not leader!!!). 
   The search Results not includes docs that have been indexed to the leader
in step 3.  
6. syncing with the active rep. 

*Expected:*
5. To stay in down status. 
   Not to handle index, commit and search requests - no servers hosting
shards!
6. Become the leader. 

Thanks.



--
View this message in context: http://lucene.472066.n3.nabble.com/solr-4-8-Leader-Problem-tp4135306.html
Sent from the Solr - User mailing list archive at Nabble.com.