[
https://issues.apache.org/jira/browse/SOLR-9320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15404456#comment-15404456
]
Nitin Sharma commented on SOLR-9320:
------------------------------------
Would be good to establish context on when this command should/can be run. In
our current version of rebalance, we use this to switch serving nodes in
production and hence the time taken to migrate a node is limited (time bound).
If this is considered an offline process, then may be serial works just fine.
I agree with Erick on throttling but we can do that at a system level (unix
traffic shaping tc etc). That will leave the bandwidth management outside the
responsibility of solr. The same node serving solr can be used to run other
services in some production setups. Keeping that outside solr will put that
onus on the maintainer. Just my $0.02
> A REPLACENODE command to decommission an existing node with another new node
> ----------------------------------------------------------------------------
>
> Key: SOLR-9320
> URL: https://issues.apache.org/jira/browse/SOLR-9320
> Project: Solr
> Issue Type: Sub-task
> Components: SolrCloud
> Reporter: Noble Paul
> Fix For: 6.1
>
> Attachments: DELETENODE.jpeg, REPLACENODE_After.jpeg,
> REPLACENODE_Before.jpeg, REPLACENODE_call_response.jpeg, SOLR-9320.patch,
> SOLR-9320.patch
>
>
> The command should accept a source node and target node. recreate the
> replicas in source node in the target and do a DLETENODE of source node
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
