-
Notifications
You must be signed in to change notification settings - Fork 740
Don't wait for TEvReadSetAck from non-existent tablets #17913
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
Don't wait for TEvReadSetAck from non-existent tablets #17913
Conversation
|
⚪ DetailsTest history | Ya make output | Test bloat
⚪ DetailsTest history | Ya make output | Test bloat | Test bloat
⚪ Test history | Ya make output | Test bloat | Test bloat | Test bloat
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
|
🟢 |
|
⚪ DetailsTest history | Ya make output | Test bloat
⚪ Test history | Ya make output | Test bloat | Test bloat
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
Don't wait for TEvReadSetAck from non-existent tablets (#17913)
Don't wait for TEvReadSetAck from non-existent tablets (#17913)
Don't wait for TEvReadSetAck from non-existent tablets (#17913)
Don't wait for TEvReadSetAck from non-existent tablets (#17913)
Changelog entry
Issue #17915
The PQ tablet forgets about the transaction only after it receives a TEvReadSetAck from all participants. Another shard may be deleted before the PQ completes the transaction (for example, due to a split table). As a result, transactions are executed, but remain in the WAIT_RS_ACKS state.
If the PQ tablet sends a TEvReadSet to a tablet that has already been deleted, it receives a TEvClientConnected with the
Deadflag in response. In this case, we consider that we have received a TEvReadSetAck.Changelog category
Description for reviewers
...