[
https://issues.apache.org/jira/browse/SOLR-4655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625606#comment-13625606
]
Mark Miller commented on SOLR-4655:
-----------------------------------
bq. Is the change as simple as using Assign.assignNode()
I think it's a bit more complicated than that - its a 62 kb patch. I think I've
simplified things overall though. The way you could override the node name or
get the address based name previously was a bit ugly. This creates one place
for corenodename to be set, rather than having various places knowing and using
the default when the core node name is null or something.
> The Overseer should assign node names by default.
> -------------------------------------------------
>
> Key: SOLR-4655
> URL: https://issues.apache.org/jira/browse/SOLR-4655
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Mark Miller
> Assignee: Mark Miller
> Fix For: 4.3, 5.0
>
> Attachments: SOLR-4655.patch
>
>
> Currently we make a unique node name by using the host address as part of the
> name. This means that if you want a node with a new address to take over, the
> node name is misleading. It's best if you set custom names for each node
> before starting your cluster. This is cumbersome though, and cannot currently
> be done with the collections API. Instead, the overseer could assign a more
> generic name such as nodeN by default. Then you can easily swap in another
> node with no pre planning and no confusion in the name.
--
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: [email protected]
For additional commands, e-mail: [email protected]
