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.

Sign up for GitHub

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

Jump to bottom

Primary lock fallen back from async commit cannot be resolved #1855

Closed

leiysky opened this issue Apr 30, 2021 · 0 comments · Fixed by #1856

Labels

severity/critical type/bug

Contributor

leiysky commented Apr 30, 2021

pingcap/tidb#24384

leiysky added type/bug severity/critical labels

leiysky self-assigned this

leiysky mentioned this issue

Fix client-c mistake setting current_ts to 0 when resolving lock for async commit #1856

Merged

solotzg closed this as completed in #1856

ti-srebot mentioned this issue

Fix client-c mistake setting current_ts to 0 when resolving lock for async commit (#1856) #1870

Merged

zhouqiang-cl unassigned leiysky

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment