Database error: "sql: transaction has already been committed or rolled back"

[theblazehen]

@tomp

OK so in your case, your cluster appears to be up and running, but I am surprised it has ever worked well because its spread over 3 different geographical locations (from what I’m interpreting its Helsinki, Germany and Spain).

Yeah, we’ve had a discussion about that before, in general it’s been reliable but slow since Heartbeat timeouts after upgrade to 4.18 - #38 by tomp

@tomp

Do you happen to know where the leader was before the upgrade?

I’m afraid not

@tomp

What is the latency between each of the sites?

Between 20 and 35 ms