You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm testing Postgres failover with Mage. If primary postgres is down, then standby is promoted to the primary, trigger is hanging infinitely, so i have to restart Mage container. In the production, i think it's not good. Is it a bug? or can you guide me?
Primary postgres down -> can't see info in the DB on UI -> standby is promoted to the primary -> can see info in the DB on UI -> running icon keep spinning -> restart Mage, it works as expected.
Mage version
0.9.71
Describe the bug
Hello Mage team,
I'm testing Postgres failover with Mage. If primary postgres is down, then standby is promoted to the primary, trigger is hanging infinitely, so i have to restart Mage container. In the production, i think it's not good. Is it a bug? or can you guide me?
Primary postgres down -> can't see info in the DB on UI -> standby is promoted to the primary -> can see info in the DB on UI -> running icon keep spinning -> restart Mage, it works as expected.
MAGE_DATABASE_CONNECTION_URL=postgresql+psycopg2://user:password@/dbname?host=HostA:PortA&host=HostB&target_session_attrs=read-write.
https://mageai.slack.com/archives/C03HTTWFEKE/p1718409165076919
To reproduce
No response
Expected behavior
If DB connection error occurs, Mage should deal with that error, then try to reconnect to available postgres DB based on MAGE_DATABASE_CONNECTION_URL
Screenshots
No response
Operating system
No response
Additional context
I haven't tested this case using Load balancer and two Postgres DB (primary and standby).
The text was updated successfully, but these errors were encountered: