Skip to content

Allow multiple BaseCouch instances to share a bucket (AKA "shared-nothing") #8

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

Closed
snej opened this issue Jan 5, 2013 · 1 comment
Closed
Milestone

Comments

@snej
Copy link
Contributor

snej commented Jan 5, 2013

For scalability, we need to support any number of BaseCouch processes sharing the same Couchbase bucket.

Here is a design wiki for this

Currently this almost works; the exception is the _changes feed. It may need to wait for changes to the database, and the mechanism it uses for this is based on in-process Go notifications. So a _changes feed request being served by one process will wait forever without noticing a database change made by another process.

To fix this we need to hook into the Couchbase Server 'TAP' feed, or else some new mechanism TBD.

@snej
Copy link
Contributor Author

snej commented Jun 7, 2013

The changes on the 'scalable' branch implemented this. It's now been merged into master.
There may still be race conditions to discover and fix.

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

No branches or pull requests

1 participant