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.

Sign up for GitHub

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

Jump to bottom

Implement quorum-based clustering #104

Open
ecton opened this issue Nov 23, 2021 · 1 comment
Open

Implement quorum-based clustering #104

ecton opened this issue Nov 23, 2021 · 1 comment
Labels
enhancement New feature or request networking Issues relating to either the networked server or client

Comments

@ecton
Copy link
Member

ecton commented Nov 23, 2021

No description provided.

@ecton ecton added the cluster label Nov 23, 2021
@ecton ecton added this to the 0.3.0 milestone Nov 23, 2021
@ecton ecton removed this from the v0.3.0 milestone Jan 18, 2022
@ecton
Copy link
Member Author

ecton commented Jan 22, 2022

A timely post by Martin Fowler on Two Phase Commit with explanations of several conflict resolution approaches.

I think BonsaiDb's approach can be quite simple due to transactions being performed in a single step. I have been trying to decide if there is a possibility for a deadlock pattern to arise given the current design. If there is, I believe either wound-wait or wait-die strategies would work for resolving it.

@ecton ecton added enhancement New feature or request networking Issues relating to either the networked server or client and removed cluster labels Jan 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request networking Issues relating to either the networked server or client
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ecton