Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

coprocessor streaming scans duplicated ranges when meeting lock #31928

Open
you06 opened this issue Jan 24, 2022 · 0 comments
Open

coprocessor streaming scans duplicated ranges when meeting lock #31928

you06 opened this issue Jan 24, 2022 · 0 comments
Labels
severity/moderate sig/execution SIG execution type/bug The issue is confirmed as a bug.

Comments

@you06
Copy link
Contributor

you06 commented Jan 24, 2022

Bug Report

Please answer these questions before submitting your issue. Thanks!

Related to #30207.

1. Minimal reproduce step (Required)

  1. Build the failpoint package and run with failpoint enabled.
make failpoint-enable
make && cd bin
GO_FAILPOINTS="github.com/pingcap/tidb/server/enableTestAPI=return(true)" tiup playground nightly --monitor=false --tiflash=0 --db.binpath=./tidb-server
  1. Prepare data with this script.

  2. Inject with 5 secs sleep before commit phase(this will not affect 1pc).

curl -X PUT -d "sleep(5000)" "http://127.0.0.1:10080/fail/tikvclient/beforeCommit"
  1. Execute the insert from the first connection then select from the second session.
Conn1 Conn2
set tidb_enable_1pc=off; set tidb_enable_streaming=1;
insert into t values(1001, 1001);
select * from t;
Query OK, 1 row affected (5.006 sec) 2153 rows in set (1.734 sec)

2. What did you expect to see? (Required)

Select statement in the second connection should return either 1,000 or 1,001 rows.

3. What did you see instead (Required)

It returns more than 1,001 rows.

4. What is your TiDB version? (Required)

master

@you06 you06 added the type/bug The issue is confirmed as a bug. label Jan 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity/moderate sig/execution SIG execution type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants