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!

More Ways To Control Your Costs With Archived Metrics | Register for Tech Talk

Tuesday, May 14, 2024  |  11AM PT / 2PM ET Register to Attend Join us for this Tech Talk and learn how to ...

.conf24 | Personalize your .conf experience with Learning Paths!

Personalize your .conf24 Experience Learning paths allow you to level up your skill sets and dive deeper ...

Threat Hunting Unlocked: How to Uplevel Your Threat Hunting With the PEAK Framework ...

WATCH NOWAs AI starts tackling low level alerts, it's more critical than ever to uplevel your threat hunting ...