Optimize the TiBinlogToTxn stage
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 291
- Forks
- 131
- Avg merge
- 5m
- Merged PRs (30d)
- 2
Description
Feature Request
Is your feature request related to a problem? Please describe:
We observed a performance bottleneck in TiBinlogToTxn (the translation) stage. We have seen binlog_drainer_queue_size is full while sync worker channel is almost emtpy.
Describe the feature you'd like:
Optimize the TiBinlogToTxn.
Describe alternatives you've considered:
Add concurrency to the TiBinlogToTxn.
Teachability, Documentation, Adoption, Migration Strategy:
N/A
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 tracing the TiBinlogToTxn stage and observing binlog_drainer_queue_size alongside the sync worker channel. Determine where translation throughput is limited and whether concurrency is appropriate. The issue is complete when the stage no longer causes the reported bottleneck and the resulting behavior is validated against the synchronization workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, data-engineering, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100