-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
goroutine stack overflow in 2pc commit #19887
Comments
The DDL job related log
The scan snapshot version ts is |
@you06 We could add some debug log for the scanner or related path, we may also need to add some sanity check for the |
@glorv This is caused by the invalid startTS input from BR, and it has been fixed. Besides, I found there still usage of |
Should fixed in br. |
Integrity check: Please comment /info to get template |
Please edit this comment to complete the following informationNot a bug
Duplicate bug
BugNote: Make Sure that 'component', and 'severity' labels are added 1. Root Cause Analysis (RCA)BR used some functions from TiDB to communite with TiKV, but BR takes snapshot using 2. SymptomThe project used TiDB got stackoverflow. 3. All Trigger ConditionsEither of the 2 conditions may lead to this error.
4. Workaround (optional)5. Affected versionsTiDB itself doesn't have this issue. BR's affected versions: [v4.0.1:v4.0.5] 6. Fixed versionsBR v4.0.6 |
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
Run br integration test failed by tidb goroutine stack overflow
See: https://internal.pingcap.net/idc-jenkins/blue/organizations/jenkins/br_ghpr_unit_and_integration_test/detail/br_ghpr_unit_and_integration_test/2853/pipeline/
2. What did you expect to see? (Required)
3. What did you see instead (Required)
4. What is your TiDB version? (Required)
release-4.0
branch with reversion3706da0fa6c7a597f3e8c69520f3ba0748dbd17f
The text was updated successfully, but these errors were encountered: