- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
search factor and replication factor not meeting and cluster master showing peers status pending after restarting one indexer directly
search factor and replication factor not meeting and cluster master showing peers status pending after restarting one indexer directly
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That's usual behavior. Allow sometime for all the ticks to go green after successful bucket replication.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@sathwikr076 - Did it resolve on its own? accept / upvote my answer if it helped.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Bit unclear. So, did you manage to recover the indexes,conf on master and pushed it to indexers?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
