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

testcase: bank2 panic when admin check table meets error #383

Open
cosven opened this issue Mar 10, 2021 · 4 comments · Fixed by #384
Open

testcase: bank2 panic when admin check table meets error #383

cosven opened this issue Mar 10, 2021 · 4 comments · Fixed by #384

Comments

@cosven
Copy link
Contributor

cosven commented Mar 10, 2021

Bug Report

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
@cosven
Copy link
Contributor Author

cosven commented Mar 10, 2021

@cosven
Copy link
Contributor Author

cosven commented Mar 29, 2021

#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

@cosven cosven reopened this Mar 29, 2021
@mahjonp
Copy link
Contributor

mahjonp commented Apr 16, 2021

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

main.log

@Thearas
Copy link
Contributor

Thearas commented Apr 16, 2021

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants