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!

.conf25 technical session recap of Observability for Gen AI: Monitoring LLM ...

If you’re unfamiliar, .conf is Splunk’s premier event where the Splunk community, customers, partners, and ...

A Season of Skills: New Splunk Courses to Light Up Your Learning Journey

There’s something special about this time of year—maybe it’s the glow of the holidays, maybe it’s the ...

Announcing the Migration of the Splunk Add-on for Microsoft Azure Inputs to ...

Announcing the Migration of the Splunk Add-on for Microsoft Azure Inputs to Officially Supported Splunk ...