[
https://issues.apache.org/jira/browse/IGNITE-23525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Sizov updated IGNITE-23525:
-----------------------------------
Description:
*Motivation*
The leases are written in meta storage in batches. If a lease needs to be
prolonged, it is prolonged to maximum possible value (lease interval / 2). This
means that all leases in batch may be prolonged by setting the expiration
timestamp to the same value, which will allow to avoid the necessity of their
prolongation in nearest future and renewal of batch. This also will allow to
compact the serialized representation of batch, because lease expiration time
will be written only once.
*Definition of done*
All leases in batch are prolonged if at least one of them needs to be prolonged.
*Implementation details*
All prolongable leases to be prolonged on any change to the leases batch. The
new expiration timestamp will be same and equal to now+leaseInterval.
Nonaccepted (new) leases will have their own expiration timestamp (which is
much bigger than standard lease interval).
When serialized, common expiration timestamp will be written to LeaseBatch
metadata only once, instead of writing it every time in each Lease.
For nonacepted (new) leases - they are believed to be rare - expiration
timestamp will be written as is.
was:
*Motivation*
The leases are written in meta storage in batches. If a lease needs to be
prolonged, it is prolonged to maximum possible value (lease interval / 2). This
means that all leases in batch may be prolonged by setting the expiration
timestamp to the same value, which will allow to avoid the necessity of their
prolongation in nearest future and renewal of batch. This also will allow to
compact the serialized representation of batch, because lease expiration time
will be written only once.
*Definition of done*
All leases in batch are prolonged if at least one of them needs to be prolonged.
> Prolong all leases in batch if at least one of them needs to be prolonged
> -------------------------------------------------------------------------
>
> Key: IGNITE-23525
> URL: https://issues.apache.org/jira/browse/IGNITE-23525
> Project: Ignite
> Issue Type: Improvement
> Reporter: Denis Chudov
> Priority: Major
> Labels: ignite-3
>
> *Motivation*
> The leases are written in meta storage in batches. If a lease needs to be
> prolonged, it is prolonged to maximum possible value (lease interval / 2).
> This means that all leases in batch may be prolonged by setting the
> expiration timestamp to the same value, which will allow to avoid the
> necessity of their prolongation in nearest future and renewal of batch. This
> also will allow to compact the serialized representation of batch, because
> lease expiration time will be written only once.
> *Definition of done*
> All leases in batch are prolonged if at least one of them needs to be
> prolonged.
> *Implementation details*
> All prolongable leases to be prolonged on any change to the leases batch. The
> new expiration timestamp will be same and equal to now+leaseInterval.
> Nonaccepted (new) leases will have their own expiration timestamp (which is
> much bigger than standard lease interval).
> When serialized, common expiration timestamp will be written to LeaseBatch
> metadata only once, instead of writing it every time in each Lease.
> For nonacepted (new) leases - they are believed to be rare - expiration
> timestamp will be written as is.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
