[
https://issues.apache.org/jira/browse/IGNITE-27903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Chudov updated IGNITE-27903:
----------------------------------
Description:
Lease waiters may occupy significant heap amount. The reason is that
PendingComparableValuesTracker is used, which tracks values separately.
Completable futures are created for every timestamp in future, which makes no
sense in this case. We may track a single future for replication group.
For awaiting primary replica, we can create completable future with timeout. It
can be completed successfully if group's future is completed, or timed out if
group lease doesn't appear in time.
was:
Lease waiters may occupy significant heap amount. The reason is that
PendingComparableValuesTracker is used, which tracks values separately.
Completable futures are created for every timestamp in future, which makes no
sense in this case. We may track a single future for replication group.
For awaiting primary replica, we can create completable future with timeout. It
can be completed successfully if group's future is completed, or timed out if
group lease doesn't appear in time.
> Lease waiters coalescing
> ------------------------
>
> Key: IGNITE-27903
> URL: https://issues.apache.org/jira/browse/IGNITE-27903
> Project: Ignite
> Issue Type: Bug
> Reporter: Denis Chudov
> Priority: Major
> Labels: ignite-3
>
> Lease waiters may occupy significant heap amount. The reason is that
> PendingComparableValuesTracker is used, which tracks values separately.
> Completable futures are created for every timestamp in future, which makes no
> sense in this case. We may track a single future for replication group.
> For awaiting primary replica, we can create completable future with timeout.
> It can be completed successfully if group's future is completed, or timed out
> if group lease doesn't appear in time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
