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!

Accelerating Observability as Code with the Splunk AI Assistant

We’ve seen in previous posts what Observability as Code (OaC) is and how it’s now essential for managing ...

Integrating Splunk Search API and Quarto to Create Reproducible Investigation ...

 Splunk is More Than Just the Web Console For Digital Forensics and Incident Response (DFIR) practitioners, ...

Congratulations to the 2025-2026 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...