Open johannesboon opened 3 years ago
Ah, this was also reported in: https://github.com/sorintlab/stolon/issues/826
@johannesboon I think the main issue is just in the docker example that uses hostnames instead of ips. When the dns like in this case becomes a round robin dns you get such issues. A working fix without using an advertising address like done in #836 could be to just use the ip of the container as listen address instead of the hostname (like done in the k8s example where we are using the pod ip).
What happened:
pg_proxy is switching multiple times per minute between 2 different IP-addresses (breaking any existing connections/transactions/queries) to the master keeper, after upgrading Docker from 19.03.13 to 20.10.6
Probably caused by: https://github.com/moby/moby/pull/39204
This sounds similar but is not directly related as the 2 IP-addresses are seen from the outside as well: https://github.com/moby/moby/issues/30963 (or at least the 2021 comment: https://github.com/moby/moby/issues/30963#issuecomment-774527403 from https://github.com/pwFoo )
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
With our setup based on this example: https://github.com/sorintlab/stolon/blob/master/examples/swarm/docker-compose-pg.yml#L24 we also defined:
we also added a placement constraints, amongst others
Anything else we need to know?:
Environment:
Main yum repositories involved:
Upgrading Docker CE from 19.x to 20.x involved these packages (I included anything I thought could be remotely related):