Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

"system ID mismatch" after restored a backup from different cluster

See original GitHub issue

When I restored a backup from another cluster to a new cluster, patroni refused to start with the following error message:

2017-08-28 20:15:55,598 CRITICAL: system ID mismatch, node postgres-recovery-patroni-recovery-0 belongs to a different cluster: 6459238215155531824 != 6414232139510366258
2017-08-28 20:15:56,063 INFO exited: patroni (exit status 1; not expected)

Is there a way to get around this when doing the restore? Thanks.

Issue Analytics

State:
Created 6 years ago
Comments:8 (2 by maintainers)

Top GitHub Comments

1reaction

anikin-aacommented, Jan 31, 2020

@ziXet in case of k8s patroni stores cluster info in config maps. You should just remove initialize key from annotations.

0reactions

ziXetcommented, Jan 30, 2020

I was using helm chart in https://github.com/kubernetes/charts/tree/master/incubator/patroni and using barman for backup and restore.

@alexeyklyukin Thanks. I was able to “hack” it by set the /service/$cluster/initialize key to the old cluster id and patroni was able to start without any error.

Hi, would you please explain how do you do this hack? I’m using patroni on kubernetes