Skip to content
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

Bug Report: Changing default of replica_net_timeout can cause issues while upgrading #15937

Closed
GuptaManan100 opened this issue May 14, 2024 · 1 comment · Fixed by #15938
Closed

Comments

@GuptaManan100
Copy link
Member

Overview of the Issue

Changing the default value of replica_net_timeout(https://dev.mysql.com/doc/refman/8.0/en/replication-options-replica.html#sysvar_replica_net_timeout) can cause issues since the heartbeat_interval value might not change. That value is only initialised when a new mysql instance starts. After that if a MySQL restarts with the updated my.cnf with the new replica_net_timeout value, then the replication between primary and replica will be broken.

Reproduction Steps

Start a v19 cluster and upgrade to v20. Restart the mysql of a replica with the new my.cnf and see that replication is broken.

Binary Version

main

Operating System and Environment details

-

Log Fragments

No response

@GuptaManan100
Copy link
Member Author

With the feature request #15880 implemented in VTOrc that can fix this configuration problem, we just need to revert the changes in #15663 and #15689 and make the default change in the next release once the VTOrc fixes are guaranteed to be present.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant