TiFlash count result is not stable using the same read tso after drop table and recreate same table
Open
@lidezhu is already working on this.
Since Jun 22, 2021.
component/storage
severity/moderate
type/bug
- Dominant language
- C++
- Stars
- 1k
- Forks
- 423
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 24
Description
After drop a table, there is a chance that tiflash's count result is not stable using some read tso. But tikv's result is stable as the following image shows.
The main test process is as follows:
- start a transaction in some thread.
- drop the target table and create a table with the same name in another thread.
- write data into the new table.
- check the count result of tikv and tiflash in the previous transaction and compare the results.
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.
Assessment
This issue has not been assessed yet.