Deployment Architecture

Bucket fixup tasks(pending). Fixup reason = "Received shutdown notification from peer"

muizash
Path Finder

We had to stop an indexer and add new one into cluster. Splunk generally automatically handles bucket replication but I am getting error. Please help

0 Karma

mloyola_splunk
Splunk Employee
Splunk Employee

In the bucket status dashboard you can see why the fixup task per bucket is in pending.
One of the reason is that, it was not roll to warm yet.

Did you put the cluster to maintenance mode and gracefully shutdown the indexer?
You have fixed up task because 1 indexer is being shutdown and it stops sending heartbeat to the Cluster master. This causes the master to detect the loss and initiate remedial action and will replace bucket copies on a downed peer by coordinating the activities to other peers.

You can check more details here:
https://docs.splunk.com/Documentation/Splunk/8.0.0/Indexer/Whathappenswhenaslavenodegoesdown

0 Karma

inawaz123
Loves-to-Learn

What is the problem here ? Is the fixup buckets are being stuck , which version of ES you are in

0 Karma
Get Updates on the Splunk Community!

Accelerating Observability as Code with the Splunk AI Assistant

We’ve seen in previous posts what Observability as Code (OaC) is and how it’s now essential for managing ...

Integrating Splunk Search API and Quarto to Create Reproducible Investigation ...

 Splunk is More Than Just the Web Console For Digital Forensics and Incident Response (DFIR) practitioners, ...

Congratulations to the 2025-2026 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...