[
https://issues.apache.org/jira/browse/IGNITE-24240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr updated IGNITE-24240:
-------------------------------
Epic Link: IGNITE-24241
> Introduce lower and upper limits for transaction timeouts
> ---------------------------------------------------------
>
> Key: IGNITE-24240
> URL: https://issues.apache.org/jira/browse/IGNITE-24240
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
>
> When a user specifies a timeout for a transaction, we might need to validate
> that it belongs to some sane interval.
> For RO transactions, dataAvailabilityTime might serve as an upper limit, On
> the other hand, the user might want to have very long RO transactions
> exceeding dataAvailabilityTime. Perhaps, we need to have 2 kinds of 'data
> availability time': a soft one and a hard one. The soft one could be used by
> the GC when calculating the candidate LWM, and the hard one would limit RO
> transaction timeouts. Anyway, it needs to be thought through.
> For RW transactions, a design is required as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
