-
Notifications
You must be signed in to change notification settings - Fork 312
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
Fix TiKV config check false alarm when data_dir is depended on #1471
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1471 +/- ##
===========================================
+ Coverage 24.85% 47.84% +22.99%
===========================================
Files 267 292 +25
Lines 21267 23161 +1894
===========================================
+ Hits 5285 11082 +5797
+ Misses 15175 10333 -4842
- Partials 807 1746 +939
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Is this argument working for all versions of TiKV on config check? |
I think so, we are using it here as well:
|
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
Are the test failures related? I don't understand them😢 |
Umm no, just retry and watch... |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: f713108
|
What problem does this PR solve?
When TiKV config check requires correct data_dir value, tiup config check will fail because it doesn't feed that information to TiKV.
What is changed and how it works?
Add extra data path parameter when doing TiKV config check.
Check List
Tests
Related changes
Release notes: