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

Server-less configuration not fault-tolerant #4

Open
pron opened this issue Jul 4, 2012 · 0 comments
Open

Server-less configuration not fault-tolerant #4

pron opened this issue Jul 4, 2012 · 0 comments
Assignees
Labels

Comments

@pron
Copy link
Contributor

pron commented Jul 4, 2012

The problem is that during item migration (getx-putx), the old owner needs to both transfer ownership to the requesting node (putx), as well as notify its slave (inv) that it is no longer the owner (of the item). If one of them (slave or peer) do not get the message and the old owner fails, the item may be lost (both peer and slave think they're not the owner) or become conflicted (both think they're the owner).

I suspect that doing this correctly would require a consensus protocol, which might make the whole thing not worthwhile. The only hope is that we could somehow take advantage of the fact that we know that the old owner has failed, i.e. that the node-switch event is received by everyone (we have consensus over that provided by ZooKeeper/JGroups).

@ghost ghost assigned pron Jul 4, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant