`endless-htap-consistency-chaos` failed
Open
@JaySon-Huang is already working on this.
Since Dec 4, 2025.
component/storage
severity/major
type/bug
- Dominant language
- C++
- Stars
- 1k
- Forks
- 423
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 24
Description
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
https://tcms.pingcap.net/dashboard/executions/plan/7916800
2. What did you expect to see? (Required)
result inconsistent tso 462501132822118401, difference: row number: 1, row1: 60509113, row2: 60509112, tikv: [60509113], tiflash: [60509112]
[2025/11/28 11:50:21.640 +08:00] [ERROR] [consistency_test.go:685] ["check consistence error"] ["db name"=db0] [sql="select count(*) from dwm_yl_rt_ssmx_bill_detail"] [realSql="select /*+ use_index(dwm_yl_rt_ssmx_bill_detail,PRIMARY) */ count(*) from dwm_yl_rt_ssmx_bill_detail"] ["prev succ"=493] [error="result inconsistent tso 462501132822118401, difference: row number: 1, row1: 60509113, row2: 60509112, tikv: [60509113], tiflash: [60509112]"] [stack="github.com/pingcap/endless/testcase/tiflash/consistency_test.checkConsistency.func1\n\t/home/jenkins/agent/workspace/endless-master-build/testcase/tiflash/consistency/consistency_test.go:685\ngithub.com/pingcap/endless/testcase/tiflash/consistency_test.checkConsistency.WithGinkgoRecover.func2\n\t/go/pkg/mod/github.com/pingcap/endless@v0.0.0-20251016101934-b4857b163a2c/pkg/util/fastfail.go:18\ngolang.org/x/sync/errgroup.(*Group).Go.func1\n\t/go/pkg/mod/golang.org/x/sync@v0.12.0/errgroup/errgroup.go:78"]
3. What did you see instead (Required)
4. What is your TiFlash version? (Required)
d0b28bd1c47167725f1a6e4111ece4b41a5e3230
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.