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
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Data Persistence in the OpenTelemetry Collector

This blog post is part of an ongoing series on OpenTelemetry. What happens if the OpenTelemetry collector ...

Introducing Splunk 10.0: Smarter, Faster, and More Powerful Than Ever

Now On Demand Whether you're managing complex deployments or looking to future-proof your data ...

Community Content Calendar, September edition

Welcome to another insightful post from our Community Content Calendar! We're thrilled to continue bringing ...