An update to this old topic since it takes time to apply for performing a restart for my client. I fixed the issue by performing a bundle restart in the Splunk cluster master. I also increased the "max_peer_build_load" and "max_peer_rep_load" values in the server.conf file to clear up existing bucket fixup tasks more quickly. Still not sure what "fsck failed exit code 24" means tho. Probably just an issue of network delay or low cpu. Reference: https://splunk.my.site.com/customer/s/article/Bucket-fixup-tasks-status-Missing-enough-suitable-candidate-to-create-searchable-copy-to-order-to-meet-replication-policy         ... View more