Deployment Architecture

Bucket replication issues - No possible srcs for replication


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)

Path Finder

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
Get Updates on the Splunk Community!

New Splunk Observability innovations: Deeper visibility and smarter alerting to ...

You asked, we delivered. Splunk Observability Cloud has several new innovations giving you deeper visibility ...

Synthetic Monitoring: Not your Grandma’s Polyester! Tech Talk: DevOps Edition

Register today and join TekStream on Tuesday, February 28 at 11am PT/2pm ET for a demonstration of Splunk ...

Instrumenting Java Websocket Messaging

Instrumenting Java Websocket MessagingThis article is a code-based discussion of passing OpenTelemetry trace ...