After enabling PG Bouncer and receiving errors like FATAL: no pg_hba.conf entry for host OR Error: connect ETIMEDOUT.
- FATAL: no_pg_hba.conf: Once you enable PgBouncer ScaleGrid will update your connection string, since your application servers will first connect to PgBouncer instead of directly to PostgreSQL, this is why the connection string will need to be updated to include the PgBouncer host and port instead of directly to your PostgreSQL.
- ETIMEDOUT occurs when the client waits for a response during the TCP handshake but receives nothing before the timeout expires (default in Node.js is usually 2-5 seconds, depending on configuration). When you enable PgBouncer the port changes to 6432 and so these timeouts would be related to the security groups settings.
- To mitigate issues after enabling PGBouncer, make sure to update your security group settings and the connection string your application is using.
Comments
0 comments
Article is closed for comments.