[
https://issues.apache.org/jira/browse/SOLR-11067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-11067:
------------------------------
Description:
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
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.
was:
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.
> REPLACENODE should make it optional to provide a target node
> ------------------------------------------------------------
>
> 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
> Assignee: Noble Paul
> Priority: Major
> Fix For: master (8.0), 7.3
>
> Attachments: SOLR-11067.patch
>
>
> 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 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
