title: SolrCloud High Availability during indexing operation
body: <p>I am testing High Availability feature of SolrCloud. I am using the following setup</p>
  
  <ul>
  <li>8 linux hosts</li>
  <li>8 Shards</li>
  <li>1 leader, 1 replica / host</li>
  <li>Using Curl for update operation</li>
  </ul>
  
  <p>I tried to index 80K documents on replicas (10K/replica in parallel). During indexing process, I stopped 4 Leader nodes. Once indexing is done, out of 80K docs only 79808 docs are indexed.</p>
  
  <p>Is this an expected behaviour ? In my opinion replica should take care of indexing if leader is down.</p>
  
  <p>If this is an expected behaviour, any steps that can be taken from the client side to avoid such a situation.</p>