planetscale / vitess-operator

Kubernetes Operator for Vitess

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Add setting to disable replication repair

enisoc opened this issue · comments

When running something like Orchestrator alongside Vitess, it's best to disable the replication repair feature of Vitess Operator so only one agent tries to fix the master. We would need to add a new field under replication to support this, since replication repair is currently always on.

I was able to test without the orchestrator that it keeps the master as read-only when the repair is disabled. I'm having some issues with Vitess + orchestrator configuration so I wasn't able to test if the race condition issue is fixed.

I've tested with vitess + orchestrator (mysql flavor) and a new master was elected without any issues.