Ecto connection pool retains stale IP after DNS change
Symptom When the IP address associated with a hostname used by an Ecto.Repo changes after the connection pool has been started, existing connections continue to resolve to the former address until the pool is recycled. The underlying behavior stems from Erlang’s :inet resolver being called only when a socket is first opened, and SSL/TLS certificate validatio
ecto
sqlalchemy