(What command will decommission a search peer from an indexer cluster?)

Question

Options

• Asplunk disablepeer --enforce-counts
• Bsplunk decommission --enforce-counts
• Csplunk offline --enforce-counts
• Dsplunk remove cluster-peers --enforce-counts

• A
  1% (1)
• B
  1% (1)
• C
  94% (66)
• D
  3% (2)

Explanation

The splunk offline --enforce-counts command is the official and documented method used to gracefully decommission a search peer (indexer) from an indexer cluster in Splunk Enterprise. This command ensures that all replication and search factors are maintained before the peer is removed. When executed, Splunk initiates a controlled shutdown process for the peer node. The Cluster Manager verifies that sufficient replicated copies of all bucket data exist across the remaining peers according to the configured replication_factor (RF) and search_factor (SF). The --enforce-counts flag specifically enforces that replication and search counts remain intact before the peer fully detaches from the cluster, ensuring no data loss or availability gap. The sequence typically includes: Validating cluster state and replication health. Rolling off the peer's data responsibilities to other peers. Removing the peer from the active cluster membership list once replication is complete. Other options like disablepeer, decommission, or remove cluster-peers are not valid Splunk commands. Therefore, the correct documented method is to use: splunk offline --enforce-counts - Indexer Clustering: Decommissioning a Peer Node - Managing Peer Nodes and Maintaining Data Availability - Splunk CLI Command Reference - splunk offline - Cluster Manager and Peer Maintenance Procedures

No community discussion yet for this question.