You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Denis Chudov (Jira)" <ji...@apache.org> on 2026/01/23 16:02:00 UTC

[jira] [Updated] (IGNITE-27657) Prototype in-memory leases

     [ https://issues.apache.org/jira/browse/IGNITE-27657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Denis Chudov updated IGNITE-27657:
----------------------------------
    Description: 
There is no need, in general, to store leases in persistent data.

Binding the leases to meta storage may cause lease expiration due to meta storage group or disk lags.

However the consistency of unexpired lease data should be preserved. If in-memory data is lost, we must wait for lease interval to create new leases.

Also, leases may be duplicated to meta storage for the sake of placement driver events' logic.

*Note:* this improvement may be done after IGNITE-27658 which may neutralize the negative effect of unexpected lease expirations.

  was:
There is no need, in general, to store leases in persistent data.

Binding the leases to meta storage may cause lease expiration due to meta storage group or disk lags.

However the consistency of unexpired lease data should be preserved. If in-memory data is lost, we must wait for lease interval to create new leases.

Also, leases may be duplicated to meta storage for the sake of placement driver events' logic.

Note: this improvement may be done after IGNITE-27658 which may neutralize the negative effect of unexpected lease expirations.


> Prototype in-memory leases
> --------------------------
>
>                 Key: IGNITE-27657
>                 URL: https://issues.apache.org/jira/browse/IGNITE-27657
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Denis Chudov
>            Priority: Major
>              Labels: ignite-3
>
> There is no need, in general, to store leases in persistent data.
> Binding the leases to meta storage may cause lease expiration due to meta storage group or disk lags.
> However the consistency of unexpired lease data should be preserved. If in-memory data is lost, we must wait for lease interval to create new leases.
> Also, leases may be duplicated to meta storage for the sake of placement driver events' logic.
> *Note:* this improvement may be done after IGNITE-27658 which may neutralize the negative effect of unexpected lease expirations.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)