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", "GracefulShutdown", or Stopped", 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", "GracefulShutdown", or "Stopped" 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-peerson 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.
Put a peer into detention
Handle manager site failure
This documentation applies to the following versions of Splunk® Enterprise: 8.1.0, 8.1.1, 8.1.2, 8.1.3, 8.1.4, 8.1.5, 8.1.6, 8.1.7, 8.1.8, 8.1.9, 8.1.10, 8.1.11, 8.1.12, 8.1.13, 8.1.14, 8.2.0, 8.2.1, 8.2.2, 8.2.3, 8.2.4, 8.2.5, 8.2.6, 8.2.7, 8.2.8, 8.2.9, 8.2.10, 8.2.11, 8.2.12, 9.0.0, 9.0.1, 9.0.2, 9.0.3, 9.0.4, 9.0.5, 9.0.6, 9.0.7, 9.1.0, 9.1.1, 9.1.2