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
Describe the bug Since readTimeout is short, it times out earlier than the switchOverTimeoutSeconds given to GetContext.
readTimeout
switchOverTimeoutSeconds
moco/pkg/dbop/replication.go
Lines 64 to 70 in ffb5b0a
In this case, the error message is as follows, and it is hard to understand that it is a timeout:
"error": "failed to failover: failed to wait GTID subset aaaa-bbbb-cccc-dddd-efgh:1-10: invalid connection",
The readTimeout setting is as follows:
moco/pkg/dbop/operator.go
Line 20 in ffb5b0a
For the same reason, failOverTimeoutSeconds is a meaningless value.
failOverTimeoutSeconds
Expected behavior Return ErrTimeout in case of timeout. switchOverTimeoutSeconds should be shorter than readTimeout.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
Since
readTimeout
is short, it times out earlier than theswitchOverTimeoutSeconds
given to GetContext.moco/pkg/dbop/replication.go
Lines 64 to 70 in ffb5b0a
In this case, the error message is as follows, and it is hard to understand that it is a timeout:
The readTimeout setting is as follows:
moco/pkg/dbop/operator.go
Line 20 in ffb5b0a
For the same reason,
failOverTimeoutSeconds
is a meaningless value.Expected behavior
Return ErrTimeout in case of timeout.
switchOverTimeoutSeconds
should be shorter thanreadTimeout
.The text was updated successfully, but these errors were encountered: