bilateral synchronization: Write conflict could happen in update mark table
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 291
- Forks
- 131
- Avg merge
- 5m
- Merged PRs (30d)
- 2
Description
Bug Report
-
What did you do?
If possible, provide a recipe for reproducing the error.
enable bilateral synchronization with two TiDB cluster. -
What did you expect to see?
update mark table without conflict. -
What did you see instead?
write conflict in TiDB log. -
Please provide the relate downstream type and version of drainer.
(rundrainer -Vin terminal to get drainer's version)
v4.0.2
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
Start by reproducing bilateral synchronization with two TiDB clusters using drainer v4.0.2, then inspect the TiDB logs and update mark table behavior around the reported write conflict. Done means the synchronization updates the mark table without producing a write conflict.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100