Automatic Step down

Hi, The query is regarding the Failover and Elections lecture. As per the lecture in a 3 node scenario, the primary steps down by itself if the other two secondaries goes down. Can anyone explain the reason for this behaviour? From a high availability perspective shouldn’t the Primary node continue to be available for the clients to function?

It’s still available in the sense that you can read from it, but you can’t write to it. And it’s no longer able to replicate data if there’s only one node available hence the need to step down to a Secondary; it can no longer guarantee data durability which is one of the conditions of replication.

1 Like

Hi @Vinoth_57269,

I hope you found @007_jb’s response helpful.

This is an intended behaviour. In this scenario, the last healthy node (ex Primary node) is just like a standalone node which is not replicating the data to other nodes and hence it is not providing the data durability guarantee.

Hope it helps!

Shubham Ranjan
Curriculum Services Engineer

1 Like