We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Description
Steps to reproduce the issue:
Describe the results you received: MySQL binlog dump thread will still exists for minutes
Describe the results you expected:
Output of ./dtle version:
./dtle version
(not available)
Additional information you deem important (e.g. issue happens only occasionally):
Additional details (log, config, job config etc):
The text was updated successfully, but these errors were encountered:
fixed in 385c441.
It is mainly affected by HeartbeatPeriod when setting up streaming.
HeartbeatPeriod
Test shows that the dump thread will be closed when
Sorry, something went wrong.
No branches or pull requests
Description
Steps to reproduce the issue:
Describe the results you received:
MySQL binlog dump thread will still exists for minutes
Describe the results you expected:
Output of
./dtle version
:Additional information you deem important (e.g. issue happens only occasionally):
Additional details (log, config, job config etc):
The text was updated successfully, but these errors were encountered: