Database Reconnect

[dustin-H]

When Aiven is switching the Database due to automatic maintenance one seems not to be able to reconnect properly.

Also, the server does not crash, which would trigger a restart and thus a reconnect.

Currently it just loses the database-connection and gets unresponsive.

[terehov]

I’ll look into that.
Meanwhile:

A pg.Pool will handle this for you, even if you never want more than one client.

brianc/node-postgres#1558

[dustin-H]

Okey, just another hint for that.

In the logs I can see some errors like this:
Error: connect ETIMEDOUT xx.xxx.xx.xxx:12345

However, Aiven is changing the IP-Address with that maintenance:

NOTE: The DNS name of the service will remain the same while maintenance is being performed, but the underlying IP address will change.

Maybe pg.Pool is not trying to connect to the DNS-Name once resolved and keeps trying to connect to the IP-Address resolved at some point before.

[terehov]

@dustin-H what should be the expected behavior? Trying to reconnect or exit the entire app? Since the state after a lost connection is “undefined”, I would prefer to just exit the entire program (and restart).

[dustin-H]

Yes, I'd also prefer just stopping the process.

[davidsparkles]

We need to check, whether this is still a problem when using Typeorm or whether they can handle it.

[dustin-H]

This is still the case with Typeorm.