[
https://issues.apache.org/jira/browse/IGNITE-28395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Chudov updated IGNITE-28395:
----------------------------------
Summary: Lease Updater accumulates concurrent in-flight invocations causing
constant CAS failures (was: Update lease map before doing lease update)
> Lease Updater accumulates concurrent in-flight invocations causing constant
> CAS failures
> ----------------------------------------------------------------------------------------
>
> Key: IGNITE-28395
> URL: https://issues.apache.org/jira/browse/IGNITE-28395
> Project: Ignite
> Issue Type: Bug
> Reporter: Denis Chudov
> Priority: Major
> Labels: ignite-3
>
> LeaseUpdater relies on lease map provided by LeaseTracker and updated via
> watch listener. But we often see issues like this:
> {code:java}
> Lease update invocation failed because of outdated lease data on this
> node.{code}
> It seems that picking the map from lease tracker is not enough when meta
> storage watch listener lags behind the real time for some reason.
> I would suggest to get the lease map from meta storage in lease updater.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
