Shalin Shekhar Mangar created SOLR-11067:
--------------------------------------------
Summary: REPLACENODE should use policy to figure out the right
node for each replica
Key: SOLR-11067
URL: https://issues.apache.org/jira/browse/SOLR-11067
Project: Solr
Issue Type: Sub-task
Security Level: Public (Default Security Level. Issues are Public)
Components: AutoScaling, SolrCloud
Reporter: Shalin Shekhar Mangar
Fix For: 7.1
The REPLACENODE API currently accepts a replacement target and moves all
replicas from the source to the given target. We can improve this by having it
support policy and figure out the right target node for each replica contained
in the source.
This can also then be a thin wrapper over nodeLost event just like how
UTILIZENODE (SOLR-9743) can be a wrapper over nodeAdded event.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
