You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by "Mark Miller (JIRA)" <ji...@apache.org> on 2017/03/14 09:25:43 UTC

[jira] [Commented] (SOLR-10279) The autoAddReplica feature can result in SolrCores being assigned new shards when using legacyCloud=false.

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

Mark Miller commented on SOLR-10279:
------------------------------------

There is also a check that breaks this and the feature to have coreNodeName be used for taking over existing registrations. I'll remove it.

> The autoAddReplica feature can result in SolrCores being assigned new shards when using legacyCloud=false.
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-10279
>                 URL: https://issues.apache.org/jira/browse/SOLR-10279
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org