[
https://issues.apache.org/jira/browse/IGNITE-23401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-23401:
------------------------------------
Description:
Read-only transaction locks Low Watermark at the given timestamp on the
coordinator, so that relevant data is not removed by GC while the transaction
is active.
However, other nodes have independent Low Watermark instances, which can move
past the read timestamp and cause the data to be removed.
To solve this, we should introduce a Global Low Watermark.
was:
Rea-only transaction locks Low Watermark at the given timestamp on the
coordinator, so that relevant data is not removed by GC while the transaction
is active.
However, other nodes have independent Low Watermark instances, which can move
past the read timestamp and cause the data to be removed.
To solve this, we should introduce a Global Low Watermark.
> Low watermark is not locked globally on RO TX
> ---------------------------------------------
>
> Key: IGNITE-23401
> URL: https://issues.apache.org/jira/browse/IGNITE-23401
> Project: Ignite
> Issue Type: Bug
> Reporter: Pavel Tupitsyn
> Priority: Critical
> Labels: ignite-3, important
> Fix For: 3.0
>
>
> Read-only transaction locks Low Watermark at the given timestamp on the
> coordinator, so that relevant data is not removed by GC while the transaction
> is active.
> However, other nodes have independent Low Watermark instances, which can move
> past the read timestamp and cause the data to be removed.
> To solve this, we should introduce a Global Low Watermark.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
