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!

Index This | I’m short for "configuration file.” What am I?

May 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with a Special ...

New Articles from Academic Learning Partners, Help Expand Lantern’s Use Case Library, ...

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Your Guide to SPL2 at .conf24!

So, you’re headed to .conf24? You’re in for a good time. Las Vegas weather is just *chef’s kiss* beautiful in ...