`DB::Exception: The task [426629878843703302,1] has been registered` after BR synchronization
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1k
- Forks
- 423
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 24
Description
How to reproduce:
- Use TiUP to bootstrap a 1pd + 1tidb + 1tikv + 1tiflash cluster
- Use BR to inject TPCH100 with 1 TiFlash replica
- execute:
echo "select count(*) from orders;" | mysql --host x.x.x.x --port yyyy -Dtpch_100(orpartsupp)
After the synchronization is just finished，there is a 100% percent chance to face the error: The task [ZZZZZZZZZZZZZZ,1] has been registered; However, the problem will disappear if one keeps retrying or waits for over 10 minutes.
Similar errors can also be encountered when executing TPCH Queries (I have tried Q1, Q9), yet after a longer waiting the exception will also resolve itself magically.
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
Reproduce the issue by bootstrapping the described TiUP cluster, loading TPCH100 with BR and a TiFlash replica, then running the orders or partsupp count query through mysql. Check whether the task-registration error persists immediately after synchronization and during TPCH queries. Done means these queries complete without the exception or unexplained waiting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, mysql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100