-
Notifications
You must be signed in to change notification settings - Fork 118
Add a flag to determine if TiFlash is enabled #351
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
Conversation
Signed-off-by: Ankita Wagh <awagh@pinterest.com>
|
@ankita25 thanks for your contribution! could you please take a look at the checklist in the PR description, remove the unnecessary checks? BTW, please add a unit test for the code. |
|
Is it required to deploy tidb cluster locally? All tests seem to be expecting that. |
marsishandsome
left a comment
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
|
/run-all-tests |
zz-jason
left a comment
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
|
/merge |
|
/run-all-tests |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
|
cherry pick to release-3.1 in PR #374 |
What problem does this PR solve?
TiKV client currently assumes that TiFlash is deployed and starts a threadpool to periodically check tiflash replica status
#350
What is changed and how it works?
Added a boolean flag to determine if tiflash is enabled . The default value is false.
Check List
Tests
Code changes
Side effects
Related changes