[
https://issues.apache.org/jira/browse/SOLR-7248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14363441#comment-14363441
]
Mark Miller commented on SOLR-7248:
-----------------------------------
Just simple stuff - some of it may already happen with legacyCloud=true, but I
know there are not enough tests for it, nor is it completely done.
Basically though, you shouldn't be able to create a core for a collection if
that collection does not exist. So for example, on startup, any core that is
part not part of a collection in zk should be removed. Likewise, if ZooKeeper
says a node should host a SolrCore and it does not, it should be created (given
their is a leader to replicate from or when using a shared filesystem).
Basically, all the individual Solr instances should make the appropriate local
adjustments to stay in sync with what ZooKeeper describes as the current
cluster.
> In legacyCloud=false mode we should check if the core was hosted on the same
> node before registering it
> --------------------------------------------------------------------------------------------------------
>
> Key: SOLR-7248
> URL: https://issues.apache.org/jira/browse/SOLR-7248
> Project: Solr
> Issue Type: Bug
> Affects Versions: 5.0
> Reporter: Varun Thacker
> Assignee: Varun Thacker
> Fix For: Trunk, 5.1
>
> Attachments: SOLR-7248.patch, SOLR-7248.patch
>
>
> Related discussion here - http://markmail.org/message/n32mxbv42hzuneyy
> Currently we check if the same coreNodeName is present in clusterstate before
> registering it. We should make this check more stringent and allow a core to
> be registered only if it the coreNodeName is present and if it's on the same
> node.
> This will ensure that junk replica folders lying around on old nodes don't
> end up registering themselves when the node gets bounced.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
