-
Notifications
You must be signed in to change notification settings - Fork 131
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
drainer/syncer: add configuration for read-timeout (#1061) #1066
drainer/syncer: add configuration for read-timeout (#1061) #1066
Conversation
[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. |
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 |
This pull request has been accepted and is ready to merge. Commit hash: 9fa142a
|
/run-unit-test |
/run-all-tests |
This is an automated cherry-pick of #1061
What problem does this PR solve?
When we meet some DDL that will cost a lot of time,
readTimeout
setting to1m
won't be enough.What is changed and how it works?
add configuration for read-timeout in drainer configuration.
Check List
Tests
Code changes
Related changes
Release note
sql.DB
configurable by[syncer.to.read-timeout]