Search head displays warning: "Search peer indexer1 has the following message: Failed to make bucket = web_page~3489_86BBCA13-9E01-4D1E-8CC5-9D201CE757A5 searchable, retry count = NNN."
On cluster manager site, it can be confirmed that the bucket mentioned does not meet the search factor.
In splunkd.log from the indexer peer, the following error and warning are seen:
ERROR ProcessTracker [27601 MainThread] - (child_516__Fsck) Fsck - idx=web_page bkt='/splunkdata/web_page/db/rb_1715087751_1715029897_3489_86BBCA13-9E01-4D1E-8CC5-9D201CE757A5' Failed to write: (but will ignore per SPL-52537 hack) bloomfilter || size manifest || .finalized
WARN ProcessTracker [27601 MainThread] - (child_15929__Fsck) Fsck - Repair bloomfilter only, index=web_page, tryWarmThenCold=1, bucket=/splunkdata/web_page/db/rb_1715087751_1715029897_3489_86BBCA13-9E01-4D1E-8CC5-9D201CE757A5, exists=1, localrc=101, failReason=Bloomfilter rebuild for bkt='/splunkdata/web_page/db/rb_1715087751_1715029897_3489_86BBCA13-9E01-4D1E-8CC5-9D201CE757A5' failed; rc=-11Run the search:
|dbinspect index=web_page | search bucketId = "web_page~3502~A93C59DE-B407-4E6E-BC74-2BEEEA08EB29"
and confirm that the replication bucket does not contain information resembles the originating bucket. For some reason not yet known, splunk fails to build bloom filter on replication bucket causing the bucket to be marked unsearchable.
Instruct splunk to rebuild the bucket in question without building the bloom filter using the following process:
1. stop splunk on the relevant indexer obtained from output of dbinspect
$SPLUNK_HOME/bin/splunk stop
2. On that indexer, run:
$SPLUNK_HOME/bin/splunk fsck repair --one-bucket --bucket-path=/splunkdata/web_page/db/rb_1715087751_1715029897_3489_86BBCA13-9E01-4D1E-8CC5-9D201CE757A5 --debug --v --backfill-never
3. Restart splunk
$SPLUNK_HOME/bin/splunk start
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
29-Sep-2026
|
Initial Release |