Splunk Enterprise

Peer Status "Stop" on CM's Indexer Clustering : Master Node Dashboard

jaracan
Communicator

Hi,

We had put one of our Peers/Indexers (Lets name it IDX2) into manual detention using the command below:
Run in IDX2
/opt/splunk/bin/splunk edit cluster-config -manual_detention on

And then, we can see on the Peer Status "ManualDetention" on CM GUI's Indexer Clustering : Master Node Dashboard.

Now, we had added some conf files on the IDX2 and restarted the instance.
Run in IDX2
/opt/splunk/bin/splunk restart

The splunkd of IDX2 is now up and running.

However, on the CM's Indexer Clustering : Master Node Dashboard, the Peer Status is "Stopped" and not fully searcheable.

We tried to execute manual detention off using command below, but it did not respond.
Run in IDX2
/opt/splunk/bin/splunk edit cluster-config -manual_detention off

Run in CM
/opt/splunk/bin/splunk edit cluster-config -peer -manual_detention off

It says it was unsuccessful.

Do we need some time for it to reflect, or the have something to check on why the peer status on CM is not reflected?

0 Karma
Get Updates on the Splunk Community!

Fastest way to demo Observability

I’ve been having a lot of fun learning about Kubernetes and Observability. I set myself an interesting ...

September Community Champions: A Shoutout to Our Contributors!

As we close the books on another fantastic month, we want to take a moment to celebrate the people who are the ...

Splunk Decoded: Service Maps vs Service Analyzer Tree View vs Flow Maps

It’s Monday morning, and your phone is buzzing with alert escalations – your customer-facing portal is running ...