[
https://issues.apache.org/jira/browse/SOLR-9320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15403350#comment-15403350
]
Noble Paul commented on SOLR-9320:
----------------------------------
Yeah, It's not in the patch. What I meant to say was the Multithreading
framework is there and the code just needs to take advantage of that.
OTOH, I wonder how performant does it need to be ? Replacing a node may take a
while and as long as it completes without timing out, is it no good enough? The
health of the system is not degraded or no action is blocked while the
REPLACENODE is happening. I think, instead of creating 500 cores on the same
node (vying for the same disk/CPU) it is better to do it serially
> 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]
