Skip to content
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

Open
indexzero opened this issue May 25, 2011 · 5 comments
Open

Feature request: specify multiple Couches for a connection #75

indexzero opened this issue May 25, 2011 · 5 comments

Comments

@indexzero
Copy link
Member

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.

@mikepb
Copy link
Contributor

mikepb commented Aug 27, 2011

You could catch the error when node dies and switch to using the backup servers then. This isn't an issue specific to cradle, but to any network connections needed by your app. cradle would get really bloated to have a feature like this. There's also the issue of when to switch back to primary...

@indexzero
Copy link
Member Author

@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.

mikepb added a commit to mikepb/cradle that referenced this issue Aug 28, 2011
@mikepb
Copy link
Contributor

mikepb commented Aug 28, 2011

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 new cradle.Connection() in the options hash.

@indexzero
Copy link
Member Author

@mikepb Thanks! Also, interesting. Have you just completely given up on merging anything back into the mainline fork?

@mikepb
Copy link
Contributor

mikepb commented Aug 28, 2011

Meh. mainline is dying...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants