timestamp incorrect after sync by binlog
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 291
- Forks
- 131
- Avg merge
- 5m
- Merged PRs (30d)
- 2
Description
Bug Report
Please answer these questions before submitting your issue. Thanks!
-
deploy and start upstream v5.0.3, enable binlog
-
start pump v6.1.0 manually
-
deploy and start downtream v6.1.0, change the time zone by
set global time_zone = "UTC" -
start drainer v6.1.0.
-
change the downtream time zone by
set global time_zone = "Asia/Shanghai" -
run the sql file
-
What did you expect to see?
select * from test.t should display the same data, but different.
upstream v5.0.3:
downstream v6.1.0:
- What did you see instead?
upstream and downtream should display as the same.
- Please provide the relate downstream type and version of drainer.
(rundrainer -Vin terminal to get drainer's version)
v6.1.0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the reported sequence with upstream v5.0.3, pump v6.1.0, downstream v6.1.0, drainer v6.1.0, and the two time zones. Compare the upstream and downstream query results, then trace the drainer/binlog timestamp handling; done means synchronized data displays the same timestamps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100