[
https://issues.apache.org/jira/browse/SOLR-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13859705#comment-13859705
]
Mark Miller commented on SOLR-5311:
-----------------------------------
This cannot be part of SolrCloud as is. It was rushed in without fully
understanding the system and with terrible tests (I had to spend a lot of time
working on them to fix them).
This implementation breaks the proper functioning of SolrCloud. I've explained
how it can be properly implemented above. There may be other options as well.
The naive option here creates many bugs and must be removed for 4.6.1.
> Avoid registering replicas which are removed
> ---------------------------------------------
>
> Key: SOLR-5311
> URL: https://issues.apache.org/jira/browse/SOLR-5311
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Noble Paul
> Assignee: Noble Paul
> Fix For: 4.6, 5.0
>
> Attachments: SOLR-5311.patch, SOLR-5311.patch, SOLR-5311.patch,
> SOLR-5311.patch, SOLR-5311.patch, SOLR-5311.patch, SOLR-5311.patch
>
>
> If a replica is removed from the clusterstate and if it comes back up it
> should not be allowed to register.
> Each core ,when comes up, checks if it was already registered and if yes is
> it still there. If not ,throw an error and do an unregister . If such a
> request come to overseer it should ignore such a core
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
