Deployment Architecture

Bucket replication issues - No possible srcs for replication

damode
Motivator

I have approx. 35k buckets under Fixup Tasks Pending (35k).

  1. Under Fixup Category Search Factor
    1. Current Status - Missing enough suitable candidates to create searchable copy in order to meet replication policy. Missing={ default:1 }
    2. Time in Fixup - 17 hour(s) 8 minute(s)
    3. Fixup Reason -  unmet rf
  2. Under Fixup Category Replication Factor
    1. Status - No possible srcs for replication
    2. Time in Fixup - 17 hour(s) 8 minute(s)
    3. Fixup Reason - unmet rf

Env. details -

  • 3 x Indexers in a cluster, 1 ES, 2 regular non-clustered SHs, 1 DS
  • RF=2
  • SF=2
  • Third indexer was just newly added 4 days ago.

Can someone please advise the cause of these issues and how I can fix this ?

Background - after adding new (third) Indexer, there was some storage issue due to which it went to automatic detention but which we eventually fixed it and brought back to cluster from detention. All Indexers are up and running. After that, to fix the above issue, based on some post I did rolling restart and restarted CM but still no change to the above.

Labels (3)

haraksin
Communicator

It appears that the best fix for this is to restart the Splunk process on the indexer master - note that restarting via the GUI does not work.

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!

Tech Talk Recap | Mastering Threat Hunting

Mastering Threat HuntingDive into the world of threat hunting, exploring the key differences between ...

Observability for AI Applications: Troubleshooting Latency

If you’re working with proprietary company data, you’re probably going to have a locally hosted LLM or many ...

Splunk AI Assistant for SPL vs. ChatGPT: Which One is Better?

In the age of AI, every tool promises to make our lives easier. From summarizing content to writing code, ...