-
Notifications
You must be signed in to change notification settings - Fork 400
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
Suggestion: Provides test suite for ensuring the storage implementation is correct #538
Comments
Good idea! One approach is to adapt the implementations in Lines 522 to 813 in 65a0062
to accept arbitrary engine. Actually, TiKV itself adapts these cases to test its own |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am currently developing a high-level Raft framework based on raft-rs, as shown below.
https://github.com/lablup/raftify
One thing I've realized while developing this framework is that even a slightly incorrect storage implementation can lead to totally unexpected bugs in certain scenarios.
It seems like openraft provides a test suite that allows the storage developers to test their own custom storage, as shown in this link to prevent such situations.
I think passing these test suite can alleviate the anxiety storage developers might have about encountering unforeseen errors in specific scenarios.
Documentation about this:
https://docs.rs/openraft/latest/openraft/docs/getting_started/index.html#ensure-the-implementation-of-raftstorage-is-correct
I think it would be very helpful if raft-rs provide a similar test suite if possible.
The text was updated successfully, but these errors were encountered: