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

Posted to dev@lucene.apache.org by "Mark Miller (JIRA)" <ji...@apache.org> on 2016/02/01 22:12:39 UTC

[jira] [Commented] (SOLR-8629) When a prospective leader attempts to sync with it's shard, we should only fail the sync due to peer sync, not necessarily other exceptions.

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

Mark Miller commented on SOLR-8629:
-----------------------------------

This may be tricky, but I'm not entirely happy with the current situation.

> When a prospective leader attempts to sync with it's shard, we should only fail the sync due to peer sync, not necessarily other exceptions.
> --------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-8629
>                 URL: https://issues.apache.org/jira/browse/SOLR-8629
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>
> Otherwise, one screwed up replica can prevent a leader even if there are 100 other good replicas.



--
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