Chris M. Hostetter created SOLR-14979:
-----------------------------------------
Summary: 'nodeName' should be configurable as a startup
option/system property
Key: SOLR-14979
URL: https://issues.apache.org/jira/browse/SOLR-14979
Project: Solr
Issue Type: Improvement
Security Level: Public (Default Security Level. Issues are Public)
Reporter: Chris M. Hostetter
Currently solr cloud nodes all use a 'nodeName' generated from the hostname +
port (+ webapp context) (ie:
{{prd-solr-xyz.region-aaa.my-company.com:8983_solr}} and then register their
nodeName as an ephemeral zk nodes in {{/live_nodes}}.
I think it would be helpful if nodes could optionally be configured to use an
arbitrary (string) node name - w/o any assumptions that it be based on the
current host/port - so that it's possible to shutdown a node and migrate it to
a new host and/or port w/o any adverse impacts on other nodes in the cluster,
or existing cluster configuration/preferences that might care about nodeNames.
This would not only make it easier to migrate solr nodes between "machines" in
cloud environments where hostnames may be based on racks/regions/etc... but it
would also make it much easier to deal with stopping/restarting solr nodes in
tests - w/o needing brittle code to hope and pray that we can re-use the same
port on restart (SOLR-13871)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
