[jira] [Commented] (SOLR-4078) Allow custom naming of nodes so that a new host:port combination can take over for a previous shard.

["Mark Miller (JIRA)" <ji...@apache.org>]

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

Mark Miller commented on SOLR-4078:
-----------------------------------

note for me: not sure i caught this one in the patch

    final String key = coreState.getStr(ZkStateReader.NODE_NAME_PROP) + "_" +  coreState.getStr(ZkStateReader.CORE_NAME_PROP);
                
> Allow custom naming of nodes so that a new host:port combination can take over for a previous shard.
> ----------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-4078
>                 URL: https://issues.apache.org/jira/browse/SOLR-4078
>             Project: Solr
>          Issue Type: New Feature
>          Components: SolrCloud
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>             Fix For: 4.1, 5.0
>
>         Attachments: SOLR-4078.patch
>
>
> Currently we auto assign a unique node name based on the host address and core name - we should let the user optionally override this so that a new host address + core name combo can take over the duties of a previous registered node.
> Especially useful for ec2 if you are not using elastic ips.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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