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
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:
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:
HI,
what do you mean by "reloading buckets". What is the master doing that it shouldn´t?
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
Did you confirm that it wasn´t restarted in the first place?
index=_internal source=splunkd.log "(build"
No restart, no results
So why would it resync with all peers?