Zeebe startup issue

Hey @fvogl

I had a small look at your config and I would like to clarify some things first.

You’re using an replication factor of 2, which is a bit sub-optimal. Is there a specific reason for it? It is wise to use an odd number of replicas, since Zeebe uses raft. See as an explanation here distributed - Why is it recommended to create clusters with odd number of nodes - Stack Overflow

Quite often when doing an upgrade of Zeebe afterwards Zeebe is not performing well. It throws warnings in the gateway PODs like this and the performance is very bad.

How long does it happen until it recovers? This might be related to the replication factor of two. If one node goes down the partition will be not available, until the replica is back.

Greets
Chris