[jira] [Commented] (SOLR-11431) Leader candidate cannot become leader if replica responds 500 to PeerSync

["Nick Shanin (Jira)" <ji...@apache.org>]

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

Nick Shanin commented on SOLR-11431:
------------------------------------

I opened PR #5002 to address this: https://github.com/apache/solr/pull/5002

> Leader candidate cannot become leader if replica responds 500 to PeerSync
> -------------------------------------------------------------------------
>
>                 Key: SOLR-11431
>                 URL: https://issues.apache.org/jira/browse/SOLR-11431
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>    Affects Versions: 7.0
>            Reporter: Mano Kovacs
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: SOLR-11431.patch
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> When leader candidate does PeerSync to all replicas, to download any missing updates, it is tolerant to failures. It uses {{cantReachIsSuccess=true}} switch which handles connection issue, 404 and 503 as success, since replicas being DOWN should not affect the process.
> However, if a replica has disk issues, the core initialization might fail and that results in {{500}} instead of {{503}}. I failing replica like that can prevent any other replicas becoming the leader.
> Proposing either:
> * Accepting {{500}} as "cant reach" so leader candidate can go on
> or
> * Changing {{SolrCoreInitializationException}} to return {{503}} instead of {{500}}
> * * this might be API change, however



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org