You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shalin Shekhar Mangar (JIRA)" <ji...@apache.org> on 2016/07/05 16:48:11 UTC

[jira] [Commented] (SOLR-9265) Add configurable node_name aliases instead of host:post_context

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

Shalin Shekhar Mangar commented on SOLR-9265:
---------------------------------------------

It'd be nice to split this issue into two parts -- one for the alias support and the other for the automatic creation of cores belonging to the replaced node.

> Add configurable node_name aliases instead of host:post_context
> ---------------------------------------------------------------
>
>                 Key: SOLR-9265
>                 URL: https://issues.apache.org/jira/browse/SOLR-9265
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Keith Laban
>
> Make it possible to give an alias name to node_name of an instance. As far as I can tell you can’t do this, it's always going to be <host>:<port>_<context>. The goals of this change are the following:
> 1) Address the node by alias in the core admin/collection apis
> 2) Be able to start a new node with the same alias and have it update clusterstate with the new base_url and suck down all the cores that the old alias was hosting. This is already (kind of) possible if you create core.properties for all the cores that you want the new node to host. However I think this bleeds a little too much of the ananotmy of the cloud into the directory structure of the solr instance. The other approach is more in the paradigm of zookeeper is truth.
> For #2 the desired behavior should be such that.
> 1) If there is already a live node with the same node_name this current node should block until that node is gone
> 2) Once there is no node with the same node name and if there are any cores assigned to that node alias they should now be hosted on the newly started node
> 3) If the old node comes back with the same alias and there is now a node in live nodes with this alias go back to #1
> Configuration should be in solr.xml such that:
> {code}
> <solr>
>   <solrcloud>
>     <str name="nodeName">${solrNodeName:}</str>
>   </solrcloud>
> <solr>
> {code}
> where the default would be "<host>:<port>_<context>" style.
> An example for requirement #1:
> {{/admin/collections?action=ADDREPLICA&collection=collection&shard=shard&node=solrNodeNameAlias}}



--
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