Splunk® Enterprise

Managing Indexers and Clusters of Indexers

Acrobat logo Download manual as PDF

Acrobat logo Download topic as PDF

Remove a peer from the manager node's list

After a peer goes down, it remains on the manager's list of peer nodes. The main effect is that it continues to appear on the manager node dashboard, although its status changes to "Down" or "GracefulShutdown", depending on how it went down.

You can use the splunk remove cluster-peers command to remove peers from the list:

splunk remove cluster-peers -peers <guid>,<guid>,<guid>,...

Note the following:

  • All peers removed must be in the "Down" or "GracefulShutdown" state.
  • You specify the peers with a comma-separated list of GUIDs, one per peer.
  • The GUIDs can be specified with or without hyphens. For example: 4EB4D230-CB8B-4DEB-AD68-CF9209A6868A and 4EB4D230CB8B4DEBAD68CF9209A6868A are both valid.
  • If any GUID on the list is invalid, because one of the GUIDs does not correlate to a downed peer, the manager aborts the entire operation.
  • You can obtain peer GUIDs by running the command splunk list cluster-peers on the manager.

You can also remove the peer from the manager's list by restarting the manager.

For information on the manager node dashboard's list of peers, see View the manager node dashboard.

Last modified on 05 October, 2020
PREVIOUS
Put a peer into detention
  NEXT
Handle manager site failure

This documentation applies to the following versions of Splunk® Enterprise: 8.1.0


Was this documentation topic helpful?

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters