[
https://issues.apache.org/jira/browse/SOLR-9320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413307#comment-15413307
]
Noble Paul commented on SOLR-9320:
----------------------------------
bq.In CollectionParams, should REPLACENODE have lock level as none? What if we
are replicaing a node and someone fires a split shard request? To be correct we
need to lock right?
REPLACENNODE just adds/removes replicas, so. it is no big deal. The operation
happens across collections, so we have no idea what to lock here
> 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
> Attachments: DELETENODE.jpeg, REPLACENODE_After.jpeg,
> REPLACENODE_Before.jpeg, REPLACENODE_call_response.jpeg, SOLR-9320.patch,
> SOLR-9320.patch, SOLR-9320.patch, SOLR-9320.patch, SOLR-9320.patch,
> 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]
