-
Notifications
You must be signed in to change notification settings - Fork 170
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adapter not failing over when db server unavailable (PostgreSQL) #32
Comments
mnelson
pushed a commit
that referenced
this issue
Jan 29, 2014
The connection issue should be fixed in 1dea246. Can you get me a full trace from the |
@mnelson Nevermind that comment (I deleted here) since it was a bad config on my side. |
It looks like 1dea246 did the trick for failing over. 😄 I'm going to close this and open a new issue to track the rescue connection bug. |
This was referenced Jan 30, 2014
bwbirdsall
pushed a commit
to cloudability/makara
that referenced
this issue
Mar 16, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
First, @mnelson nice work on this adapter!
Similar to #27 I am using PostgreSQL 9.2 with a master and slave database server. The issue I'm running into is testing the adapter's ability to switch to the master when the slave becomes unavailable.
From the README:
The scenario I'm testing is starting the application with both database servers available:
/sign_up
/sign_up
After I start the slave database server again, the query works okay:
Here is my
database.yml
:One other issue is the
rescue_connection_failures
parameter./sign_up
and receive 200 OK/sign_up
againLet me know if you need more data, testing. Thanks!
The text was updated successfully, but these errors were encountered: