Deployment Architecture

Fixup Tasks (Pending) are stuck with bucket status: "cannot fix up search factor as bucket is not serviceable;"

keio_splunk
Splunk Employee
Splunk Employee

Fixup tasks (Pending) for our indexer cluster could not be fixed and the bucket current status is reporting: "cannot fix up search factor as bucket is not serviceable;".

WARN message in splunkd.log:
WARN CMMaster - event=handleSyncError bid=network~xxx~xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx src=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx tgt=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

alt text

0 Karma
1 Solution

keio_splunk
Splunk Employee
Splunk Employee

The pending bucket status are cleared after opening the management port (8089) between the indexers. It is a requirement for the management port to be opened between the indexers. Refer to "Ports that the cluster nodes use" in Splunk Documentation:

https://docs.splunk.com/Documentation/Splunk/7.2.3/Indexer/Systemrequirements#Ports_that_the_cluster...

View solution in original post

0 Karma

keio_splunk
Splunk Employee
Splunk Employee

The pending bucket status are cleared after opening the management port (8089) between the indexers. It is a requirement for the management port to be opened between the indexers. Refer to "Ports that the cluster nodes use" in Splunk Documentation:

https://docs.splunk.com/Documentation/Splunk/7.2.3/Indexer/Systemrequirements#Ports_that_the_cluster...

0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...