Splunk IT Service Intelligence

What could be a reason for the cluster taking so long before an old captain is downgraded?

FreekMulders
New Member

In my cluster with 3 peers I brought down an availability zone at 10:05 containing the shc_captain.
The other two members were working fine.
At around 10:30 a new captain was elected and my old captain was downgraded.

If I bring down the single captain, a new captain is elected within 2 minutes.

What could be a reason for my cluster taking so long before an old captain is downgraded?

0 Karma

codebuilder
Influencer

How long was the captain down? If you were running on two clustered search heads only for any period of time it is possible that the cluster encountered a split-brain situation. With only two nodes, a quorum can't be reached so neither is able to (quickly) decide/vote on who should be captain.

----
An upvote would be appreciated and Accept Solution if it helps!
0 Karma
Get Updates on the Splunk Community!

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics GA in US-AWS!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...