set read timestamp to a future time error found by sysbench

[owlsome2501]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

Run sysbench oltp_delete,oltp_update_non_index,oltp_update_index or select_random_ranges workload.

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

No error.

3. What did you see instead (Required)

sysbench report error.

sysbench 1.0.20 (using bundled LuaJIT 2.1.0-beta2)

Running the test with following options:
Number of threads: 100
Report intermediate results every 10 second(s)
Initializing random number generator from current time


Initializing worker threads...

Threads started!

[ 10s ] thds: 100 tps: 25261.30 qps: 25261.30 (r/w/o: 0.00/24503.21/758.09) lat (ms,95%): 4.74 err/s: 0.00 reconn/s: 0.00
[ 20s ] thds: 100 tps: 25155.24 qps: 25155.24 (r/w/o: 0.00/23008.23/2147.01) lat (ms,95%): 4.65 err/s: 0.00 reconn/s: 0.00
[ 30s ] thds: 100 tps: 25376.70 qps: 25376.70 (r/w/o: 0.00/21902.70/3474.00) lat (ms,95%): 4.82 err/s: 0.00 reconn/s: 0.00
[ 40s ] thds: 100 tps: 26328.49 qps: 26328.49 (r/w/o: 0.00/21448.21/4880.28) lat (ms,95%): 4.57 err/s: 0.00 reconn/s: 0.00
[ 50s ] thds: 100 tps: 26691.75 qps: 26691.75 (r/w/o: 0.00/20451.54/6240.21) lat (ms,95%): 4.49 err/s: 0.00 reconn/s: 0.00
[ 60s ] thds: 100 tps: 28206.85 qps: 28206.85 (r/w/o: 0.00/20410.24/7796.61) lat (ms,95%): 4.57 err/s: 0.00 reconn/s: 0.00
[ 70s ] thds: 100 tps: 33543.35 qps: 33543.35 (r/w/o: 0.00/22778.34/10765.02) lat (ms,95%): 4.74 err/s: 0.00 reconn/s: 0.00
[ 80s ] thds: 100 tps: 34209.88 qps: 34209.88 (r/w/o: 0.00/21674.78/12535.09) lat (ms,95%): 4.41 err/s: 0.00 reconn/s: 0.00
[ 90s ] thds: 100 tps: 35527.88 qps: 35527.88 (r/w/o: 0.00/21013.19/14514.69) lat (ms,95%): 4.33 err/s: 0.00 reconn/s: 0.00
[ 100s ] thds: 100 tps: 34112.81 qps: 34112.81 (r/w/o: 0.00/18934.40/15178.42) lat (ms,95%): 4.49 err/s: 0.00 reconn/s: 0.00
[ 110s ] thds: 100 tps: 37932.91 qps: 37932.91 (r/w/o: 0.00/19769.70/18163.20) lat (ms,95%): 4.33 err/s: 0.00 reconn/s: 0.00
[ 120s ] thds: 100 tps: 32360.17 qps: 32360.07 (r/w/o: 0.00/15845.74/16514.34) lat (ms,95%): 4.49 err/s: 0.00 reconn/s: 0.00
[ 130s ] thds: 100 tps: 33077.06 qps: 33077.16 (r/w/o: 0.00/15397.03/17680.13) lat (ms,95%): 4.49 err/s: 0.00 reconn/s: 0.00
[ 140s ] thds: 100 tps: 40095.99 qps: 40095.99 (r/w/o: 0.00/17713.14/22382.85) lat (ms,95%): 4.18 err/s: 0.00 reconn/s: 0.00
[ 150s ] thds: 100 tps: 41003.74 qps: 41003.74 (r/w/o: 0.00/17060.72/23943.02) lat (ms,95%): 4.41 err/s: 0.00 reconn/s: 0.00
FATAL: mysql_stmt_execute() returned error 1105 (cannot set read timestamp to a future time, readTS: 454793976924602994, currentTS: 454793976924602989) for query 'DELETE FROM sbtest18 WHERE id=?'
FATAL: `thread_run' function failed: /usr/share/sysbench/oltp_delete.lua:33: SQL error, errno = 1105, state = 'HY000': cannot set read timestamp to a future time, readTS: 454793976924602994, currentTS: 454793976924602989

This bug was initially discovered in commit 0bf3e01.

4. What is your TiDB version? (Required)

0bf3e01
tikv/tikv@7ef4aa9
tikv/pd@7889b67

[jebter]

Can more information be provided? For example, TiDB logs, etc.