tipocket testcase: bank2 panic when admin check table meets error

testcase: bank2 panic when admin check table meets error

Open cosven opened this issue 3 years ago • 4 comments

What did you do?

Run bank2 testcase with nemesis.

What did you expect to see?

The case should only fail when there is an inconsistency.

What did you see instead?

The case failed due to other error.

2021/03/09 07:12:40 bank2.go:331: [fatal] [bank2] ADMIN CHECK TABLE bank2_accounts fails: invalid connection

Mar 10 '21 01:03 cosven

cc @sticnarf

https://github.com/pingcap/tipocket/pull/372/files#diff-723408ebaf3839a713263e10300c4cddecbaf6ad7cfb6dbdcd6a9ccbac56ee25R327

Mar 10 '21 01:03 cosven

#384 handled two errors and I met a new error 🌚

2021/03/27 15:29:11 client.go:336: [fatal] [bank2] ADMIN CHECK TABLE bank2_accounts fails: Error 1105: context deadline exceeded

Mar 29 '21 03:03 cosven

And there is another panic log that I often see:

2021/04/15 06:13:17 client.go:336: [fatal] [bank2] ADMIN CHECK TABLE bank2_accounts fails: Error 1105: no leader

Apr 16 '21 02:04 mahjonp

And I found another:

2021/04/16 02:48:12 client.go:336: [fatal] [bank2] ADMIN CHECK TABLE bank2_accounts fails: Error 1105: redirect failed

Apr 16 '21 10:04 Thearas