Skip to content
This repository has been archived by the owner on Nov 24, 2023. It is now read-only.

found error when get sql_mode from binlog status_vars #1275

Closed
lance6716 opened this issue Nov 4, 2020 · 1 comment · Fixed by #1298
Closed

found error when get sql_mode from binlog status_vars #1275

lance6716 opened this issue Nov 4, 2020 · 1 comment · Fixed by #1298
Assignees
Labels
severity/minor type/bug This issue is a bug report

Comments

@lance6716
Copy link
Collaborator

Bug Report

Please answer these questions before submitting your issue. Thanks!

  1. What did you do? If possible, provide a recipe for reproducing the error.
    https://asktug.com/t/topic/63371

  2. What did you expect to see?

  3. What did you see instead?

[2020/11/02 17:06:20.040 +08:00] [WARN] [syncer.go:1676] [“found error when get sql_mode from binlog status_vars”] [error="[code=11117:class=functional:scope=internal:level=medium], Message: fail to parse binglog status_vars: [0 0 0 0 0 1 0 0 160 85 0 0 0 0 6 3 115 116 100 4 45 0 45 0 33 0 12 254], offset: 28, RawCause: EOF"]

  1. Versions of the cluster

    • DM version (run dmctl -V or dm-worker -V or dm-master -V):
@csuzhangxc csuzhangxc added severity/minor type/bug This issue is a bug report labels Nov 4, 2020
@lance6716
Copy link
Collaborator Author

the status_vars is (formatted)

0 0 0 0 0 
1 0 0 160 85 0 0 0 0 
6 3 115 116 100 
4 45 0 45 0 33 0 
12 254

last 12 represent Q_UPDATED_DB_NAMES, which means 254 should be understood as "there're 254 following zero-terminated string" 🤔

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
severity/minor type/bug This issue is a bug report
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants