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

Figure out Jepsen behaviour for unavailable cluster #29

Open
MathieuBordere opened this issue Sep 20, 2022 · 1 comment
Open

Figure out Jepsen behaviour for unavailable cluster #29

MathieuBordere opened this issue Sep 20, 2022 · 1 comment
Labels
question Further information is requested

Comments

@MathieuBordere
Copy link
Contributor

Find out if Jepsen reports an error when a theoretically available cluster is unavailable.

@cole-miller
Copy link
Contributor

Just brainstorming a bit about this. I'm imagining a situation like: we do some damage to the cluster, then heal it, and we expect that afterward our requests will start to complete successfully again (availability). I do not think the Jepsen checkers that we're using right now can test for this kind of thing; they're looking for either anomalies in the history of operations or red flags like assertion failures, core dumps, and uncaught exceptions. The availability check, and the circumstances under which we expect a cluster to be available, seem like they'd be pretty specific to each distributed system, and we'll need to write our own logic to implement them for dqlite.

@MathieuBordere MathieuBordere added the question Further information is requested label Jun 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants