You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Noble Paul (JIRA)" <ji...@apache.org> on 2015/03/16 13:52:38 UTC

[jira] [Issue Comment Deleted] (SOLR-7248) In legacyCloud=false mode we should check if the core was hosted on the same node before registering it

     [ https://issues.apache.org/jira/browse/SOLR-7248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Noble Paul updated SOLR-7248:
-----------------------------
    Comment: was deleted

(was: Why is there a timed loop? Why not a single attempt?)

> 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
>
>
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org