You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Table deletion during the transaction is writing data to it could cause the transaction to hang in memory.
Because the transaction coordinator is unable to apply intents at the tablet of this table.
The text was updated successfully, but these errors were encountered:
Summary:
When a tablet involved in a transaction is deleted, we could get into a
situation when the transaction cannot be fully applied. This
transaction will stay in its transaction coordinator and prevent status
tablet Raft logs from being cleaned.
Fixed by handling such cases by pretending that the transaction was
applied to the deleted tablet.
Also improved log anchor tracking in the tablet server WebUI, and fixed
potential issues of unsafe modification of a multi-index container
by using the `modify` function with an iterator and a lambda.
Test Plan: ybd --gtest_filter QLTransactionTest.DeleteTableDuringWrite
Reviewers: bogdan, mikhail
Reviewed By: mikhail
Subscribers: ybase
Differential Revision: https://phabricator.dev.yugabyte.com/D8084
Table deletion during the transaction is writing data to it could cause the transaction to hang in memory.
Because the transaction coordinator is unable to apply intents at the tablet of this table.
The text was updated successfully, but these errors were encountered: