Separate handle thread for SchemaSyncer
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1k
- Forks
- 423
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 24
Description
Currently, both storage layer and SchemaSyncer use the Context::getBackgroundPool to handle tasks. And since there will be heavy tasks in storage layer, the tasks of SchemaSyncer could be delayed. It is better to use a different thread to handle tasks in SchemaSyncer.
Contributor guide
No contributing guide indexed for this repository
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 storage layer and SchemaSyncer uses of Context::getBackgroundPool, then inspect how their tasks are scheduled. Done means SchemaSyncer tasks use a separate thread or pool and are no longer delayed by heavy storage-layer work; add coverage for the scheduling behavior if the existing test structure supports it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100