Skip to content

Commit c08d59b

Browse files
epughCopilot
andcommitted
SOLR-18140: Try to bandaid the DELETENODE docs for a broken API (#4170)
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
1 parent ee05702 commit c08d59b

1 file changed

Lines changed: 7 additions & 2 deletions

File tree

solr/solr-ref-guide/modules/deployment-guide/pages/cluster-node-management.adoc

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -667,7 +667,7 @@ Examining the clusterstate after issuing this call should show exactly one repli
667667
== Migrate Replicas
668668

669669
Migrate all replicas off of a given set of source nodes.
670-
+
670+
671671
If more than one node is used as a targetNode (either explicitly, or by default), then the configured
672672
xref:configuration-guide:replica-placement-plugins.adoc[Replica Placement Plugin] will be used to determine
673673
which targetNode should be used for each migrated replica.
@@ -862,7 +862,12 @@ So don't perform other collection operations in this period.
862862
== DELETENODE: Delete Replicas in a Node
863863

864864
Deletes all replicas of all collections in that node.
865-
Please note that the node itself will remain as a live node after this operation.
865+
Please note that the node itself will remain as a live node after this operation if it is currently functioning.
866+
867+
[TIP]
868+
====
869+
If the node is currently down and you aren't bringing it back, then this command removes that node's replica entries from the cluster state (ZooKeeper), cleaning up references to its replicas. It does not change the node's liveness in `/live_nodes`, and the node may still rejoin the cluster if it is started again later.
870+
====
866871

867872
[tabs#deletenode-request]
868873
======

0 commit comments

Comments
 (0)