You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by "Grant Ingersoll (JIRA)" <ji...@apache.org> on 2017/01/25 23:59:26 UTC

[jira] [Commented] (SOLR-10041) Leader Initiated Recovery happening when the leader also fails to index the content

    [ https://issues.apache.org/jira/browse/SOLR-10041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15838856#comment-15838856 ] 

Grant Ingersoll commented on SOLR-10041:
----------------------------------------

If the leader can't index the docs, it shouldn't cause the replicas to go into recovery.

> Leader Initiated Recovery happening when the leader also fails to index the content
> -----------------------------------------------------------------------------------
>
>                 Key: SOLR-10041
>                 URL: https://issues.apache.org/jira/browse/SOLR-10041
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: SolrCloud
>            Reporter: Grant Ingersoll
>             Fix For: 6.3
>
>
> 1 shard, 3 replica setup.  Documents are being fairly rapidly sent in for indexing which are being rejected (due to a too long of a string field) by the leader, which is then cascading outwards to put the replicas into Leader Initiated Recovery, from which they never recover.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org