Deployment Architecture

Removing a Rogue Peer in Master Node

ezajac
Path Finder

I have a clustered environment and using a Master Node to handle replication. One of my peers crashed and I had to restore Splunk on that server. That is all complete and I have rejoined the peer to the cluster. The host name is different but the IP has been assigned to the rebuilt server. How do I remove the rogue server from the Master Node?

Tags (1)

mahamed_splunk
Splunk Employee
Splunk Employee

The master retains the list of all peers connected to it and keeps the list for ever. That's why even after you removed the peer, it still lists them with the status of 'Down'.

One workaround to clear this list is to restart the master.

0 Karma

ezajac
Path Finder

It doesn't report the server as down, it reports it as "UP" in addition to the new server.

0 Karma
Get Updates on the Splunk Community!

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...