Failed to make bucket searchable, Bad Splunk Support advice?

[jfaldmomacu]

I've been getting this error for a few weeks.

Search peer <indexer> has the following message: Failed to make bucket = main~5360~4D6B6D21-6F08-44EA-B793-EFEB8C344E21 searchable, retry count = 743.

I have a case open with Splunk Support and I wanted to know if their logic or feedback is sound. After stopping the indexer I ran fsck and saw multiple buckets have needed to be rebuilt. They all rebuilt successfully except the one was in the error message. 

After sharing this information and the logs with Support I was told that "For a single bucket you can ignore this warning. Data will still be searchable for this bucket. "

So, should I think all is well because Support told me so and ignore the Health of Splunk Deployment report that shows the "red exclamation mark" icons for Buckets and Data Durability?

[Stefanie]

I may not be able to assist but I just wanted to mention that Splunk support has also told me to "ignore" some of those health check items. We ended up having to have a tech from Splunk come onsite to address some of these issues. 

My suggestion would be to spin up a new indexer to replace the indexer with that corrupted bucket.