TiFlash Count Error

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: TiFlash count 报错

| username: GreenGuan

Has anyone encountered this error with TiFlash? The business scenario involves updating tabA and then querying tabA. I also saw related errors in the forum and feel this might be a bug.

Version v5.0.3
SQL statement, sometimes successful, sometimes fails.
SELECT count(*) FROM tabA WHERE (col1 = ?) AND (col2 = ?)

[conn.go:812] [“command dispatched failed”] [conn=2513039] [connInfo=“id:2513039, addr:xxxxx:15927 status:10, collation:utf8mb4_general_ci, user:bi”] [command=Execute] [status=“inTxn:0, autocommit:1”] [sql=“SELECT count(*) FROM tabA WHERE (col1 = ?) AND (col2 = ?) [arguments: (40895, 42976)]”] [txn_mode=PESSIMISTIC] [err=“other error: [FLASH:Coprocessor:BadRequest] grpc::Status DB::BatchCoprocessorHandler::execute(): contain duplicate region 8853780
github.com/pingcap/tidb/store/copr.(*batchCopIterator).handleBatchCopResponse
\t/home/jenkins/agent/workspace/optimization-build-tidb-linux-amd/go/src/github.com/pingcap/tidb/store/copr/batch_coprocessor.go:570
github.com/pingcap/tidb/store/copr.(*batchCopIterator).handleStreamedBatchCopResponse
\t/home/jenkins/agent/workspace/optimization-build-tidb-linux-amd/go/src/github.com/pingcap/tidb/store/copr/batch_coprocessor.go:543
github.com/pingcap/tidb/store/copr.(*batchCopIterator).handleTaskOnce
\t/home/jenkins/agent/workspace/optimization-build-tidb-linux-amd/go/src/github.com/pingcap/tidb/store/copr/batch_coprocessor.go:532
github.com/pingcap/tidb/store/copr.(batchCopIterator).handleTask
\t/home/jenkins/agent/workspace/optimization-build-tidb-linux-amd/go/src/github.com/pingcap/tidb/store/copr/batch_coprocessor.go:468
runtime.goexit
\t/usr/local/go/src/runtime/asm_amd64.s:1357
SELECT count(
) FROM tabA WHERE (col1 = ?) AND (col2 = ?) [arguments: (40895, 42976)]”]

| username: h5n1 | Original post link

It seems to be this one.

| username: GreenGuan | Original post link

It looks like it was fixed after version 5.1.

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. No new replies are allowed.