-
Notifications
You must be signed in to change notification settings - Fork 182
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
Feature request: specify multiple Couches for a connection #75
Comments
You could catch the error when node dies and switch to using the backup servers then. This isn't an issue specific to |
@mikepb I don't think it would "bloat" the library, but you're probably right that it should be a separate library that cradle could later take as an upstream dependency. |
Be aware that I don't plan on using this feature, so I won't find any bugs. Also note that you must now provide host arguments to |
@mikepb Thanks! Also, interesting. Have you just completely given up on merging anything back into the mainline fork? |
Meh. mainline is dying... |
We had an outage today at Nodejitsu. The physical hardware for our Couch server at Rackspace went down. We didn't have replication setup, but now we do.
In these doomsday scenarios it would have been nice to be able to specify both the primary and backup CouchDb servers in the cradle.Connection instance and have it automatically begin to failover. I don't see any other way to solve these kinds of problems.
The text was updated successfully, but these errors were encountered: