Deployment Architecture

search factor and replication factor not meeting and cluster master showing peers status pending after restarting one indexer directly

sathwikr076
Communicator

search factor and replication factor not meeting and cluster master showing peers status pending after restarting one indexer directly

Tags (2)
0 Karma

nareshinsvu
Builder

That's usual behavior. Allow sometime for all the ticks to go green after successful bucket replication.

nareshinsvu
Builder

@sathwikr076 - Did it resolve on its own? accept / upvote my answer if it helped.

0 Karma

sathwikr076
Communicator

Hi, I am sorry. there were few indexes which are removed from the indexes.conf but they are not done properly. when one indexer got restart the cluster master started searching for those missing indexes which caused the peers status to be pending.

0 Karma

nareshinsvu
Builder

Bit unclear. So, did you manage to recover the indexes,conf on master and pushed it to indexers?

0 Karma

sathwikr076
Communicator

we opened a case with splunk support and they cleaned the indexes which are no configured properly and did a rolling restart. After that everything was ok.

0 Karma
Get Updates on the Splunk Community!

The Splunk Success Framework: Your Guide to Successful Splunk Implementations

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

Splunk Training for All: Meet Aspiring Cybersecurity Analyst, Marc Alicea

Splunk Education believes in the value of training and certification in today’s rapidly-changing data-driven ...

Investigate Security and Threat Detection with VirusTotal and Splunk Integration

As security threats and their complexities surge, security analysts deal with increased challenges and ...