Hi @balaji.ramaswamy ,
We are running Dremio in Kubernetes cluster using helm chart with below configurations
We are testing when master node goes down. How secondary coordinator reacts and take over as the new master. However, in our case when master coordinator is going down then secondary coordinator is not coming into action.
Thanks,
Ayush Goyal
@Ayush.goyal The secondary coordinator here is only to help if there are too many concurrent queries submitted and planning takes longer. This is not a secondary to the master. Secondary coordinator only works for JDBC/ODBC queries
Now coming back to your original question, In Kubernetes world, when the master pod goes down, Kubernetes should automatically bring up another master pod automatically. Is that not happening in your case?