Kirill Sizov created IGNITE-20395:
--------------------------------------
Summary: Wait for write intent cleanup in RW transaction
Key: IGNITE-20395
URL: https://issues.apache.org/jira/browse/IGNITE-20395
Project: Ignite
Issue Type: Task
Reporter: Kirill Sizov
If a transaction was committed/aborted, but the cleanup operation was not
performed on a node for any reason, the write intent entries still present in
the storage.
When an RO transaction sees such entries, no matter whether on primary or on
any other node, it performs write intent resolution and returns the correct
result.
When an RW transaction sees write intents (happens on primary only), it also
performs write intent resolution. But any following change of the rows having
write intents will result in a storage exception because we don't support more
than one write intent per row.
IGNITE-20041 added a way to trigger async write intent cleanup on the node that
executes write intent resolution.
*We need to extend this functionality with the following(Definition of done):*
# If this is a primary replica and we are executing an RW transaction that has
already performed write intent resolution, we need to synchronously wait for a
pending cleanup of the affected rows to be able to safely change the storage.
# The cleanup operation after resolution is local, not distributed - if a
primary replica has been cleaned up, the other replicas will still have write
intents in their storages. We need to perform the cleanup on other nodes as
well.
Imagine the case when there are thee replicas, A, B and C. A is primary.
A following RW transaction will successfully execute on primary since it had
its storage cleaned, but when replicating on B and C it will result in an
exception.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
