[
https://issues.apache.org/jira/browse/SOLR-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13858860#comment-13858860
]
Mark Miller commented on SOLR-5311:
-----------------------------------
You can't count on the coreNodeName to determine if a core was removed or not.
The whole thing is much tricker than this anyway - when cores are controlled by
the user, you can't yet tell what should exist or not, just what states are
published. Doing something better is more difficult than what is done with this
patch.
> 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
