What would trigger Indexer Cluster Master restart?

[tkw03]

So my indexer cluster master seems to be reloading all of the buckets. I didn't initiate a restart of the master or a rolling restart of the cluster. Is there anything else that would trigger either automatically?

Thanks for the input

[mdillon_splunk · Accepted solution]

Is it possible you had a network interruption from your Cluster Master ?
Has this situation only happened the once ?
Check for disk I/O errors, or NIC errors on your Cluster Master around the time the peers were being added back.

Note: Cluster heartbeats have improved with more recent Splunk versions:

https://conf.splunk.com/files/2017/slides/scaling-indexer-clustering-5-million-unique-buckets-and-be...

[dkeck]

HI,

what do you mean by "reloading buckets". What is the master doing that it shouldn´t?

[tkw03]

What I mean is it looks like the master got restarted as it went into making peers check back in and re-meeting rep factor and search factor

[dkeck]

Did you confirm that it wasn´t restarted in the first place?

index=_internal source=splunkd.log "(build"

[tkw03]

No restart, no results

So why would it resync with all peers?