-
Notifications
You must be signed in to change notification settings - Fork 308
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
test: add write test for region failover #1673
test: add write test for region failover #1673
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #1673 +/- ##
===========================================
- Coverage 85.72% 85.52% -0.21%
===========================================
Files 573 573
Lines 91963 92033 +70
===========================================
- Hits 78839 78707 -132
- Misses 13124 13326 +202 |
68d2988
to
41eb878
Compare
cbd8f29
to
1bf81ab
Compare
ea51523
to
f25c0e7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@@ -17,5 +17,9 @@ mod grpc; | |||
#[macro_use] | |||
mod http; | |||
|
|||
grpc_tests!(File, S3, S3WithCache, Oss, Azblob); | |||
http_tests!(File, S3, S3WithCache, Oss, Azblob); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch! I think that was because I didn't rebase the PR to the latest develop branch. I'm going fix it 👀 Thks @NiwakaDev
* test: add write test for region failover * test: add written data assertion after failover * test: support more storage types
I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
Test datanode nodes writing after region failover
Checklist
Refer to a related PR or issue link (optional)
#1126