Deployment Architecture

Fixup Tasks - Pending - streaming failure, failing=tgt

dtrust
New Member

Have Indexer Cluster. Have settings set to Search Factor 2, Replication Factor 3. I have 5 Indexer Peers at the moment. I'm getting the following messages on a number of buckets within the "Fixup Tasks - Pending". They don't seem to be going away after a number of hours.

Fixup Reason: streaming failure - src=XXXXXX tgt=XXXX failing=tgt

Current Status: Missing enough suitable candidates to create replicated copy in order to meet replication policy. Missing=( default: 1 )

What has gone wrong here?

Labels (1)
0 Karma

kumar493
Path Finder

I have the same issue did you able to solve this issue.

0 Karma

isoutamo
SplunkTrust
SplunkTrust
0 Karma

kumar493
Path Finder

Hi soutamo , 

Their are hundres of buckets , is their a way we can do all buckets at once , What i did so far is i applied retention policy to remove all data in index , but whenever new data is generating again those buckets are not replicating.

0 Karma

isoutamo
SplunkTrust
SplunkTrust
The easiest way to roll all buckets is doing rolling restart of cluster.
Another way is to make rest query to get those index names and then use map to do roll of individual index.
0 Karma
Get Updates on the Splunk Community!

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...