[
https://issues.apache.org/jira/browse/IGNITE-27651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Scherbakov updated IGNITE-27651:
---------------------------------------
Summary: Implement client liveness detection for a directly mapped
transaction (was: Implement client liveness detection for directly mapped
transaction)
> Implement client liveness detection for a directly mapped transaction
> ---------------------------------------------------------------------
>
> Key: IGNITE-27651
> URL: https://issues.apache.org/jira/browse/IGNITE-27651
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexey Scherbakov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.2
>
>
> Currently directly mapped transactions rely on transaction timeouts to
> cleanup locks in case of client failure (which serves as a lightweight
> coordinator).
> This will not work in case of very big timeouts.
> We need to implement some kind of liveness detection for a client.
> A quick solution would be setting the upper bound for tx timeouts.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
