[
https://issues.apache.org/jira/browse/IGNITE-20157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-20157:
-------------------------------------
Summary: Share context details to ease replication timeout exception
analysis (was: Add extra details to ease replication timeout exception
analysis)
> Share context details to ease replication timeout exception analysis
> --------------------------------------------------------------------
>
> Key: IGNITE-20157
> URL: https://issues.apache.org/jira/browse/IGNITE-20157
> Project: Ignite
> Issue Type: Improvement
> Reporter: Denis Chudov
> Priority: Major
> Labels: ignite-3
>
> *Motivation*
> Currently we have lock timeouts only for specific implementations of
> DeadlockPreventionPolicy. In the same time, we have transaction request
> timeouts. It makes no sense for such requests to wait for acquiring locks
> longer than request timeout.
> *Definition of done*
> Future returned by LockManager#acquire is completed exceptionally if the lock
> was not acquired in some time interval (lock acquisition timeout).
> *Implementation notes*
> This exception (or its message) should differ from the exception thrown
> because of deadlock prevention policy with timeout.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
