You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ivan Bessonov (Jira)" <ji...@apache.org> on 2025/11/10 13:44:00 UTC
[jira] [Updated] (IGNITE-26995) Enrich MvPartitionStorage.Locker with a "stop" hint
[ https://issues.apache.org/jira/browse/IGNITE-26995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Bessonov updated IGNITE-26995:
-----------------------------------
Component/s: storage engines ai3
> Enrich MvPartitionStorage.Locker with a "stop" hint
> ---------------------------------------------------
>
> Key: IGNITE-26995
> URL: https://issues.apache.org/jira/browse/IGNITE-26995
> Project: Ignite
> Issue Type: Improvement
> Components: storage engines ai3
> Reporter: Ivan Bessonov
> Assignee: Ivan Bessonov
> Priority: Major
> Labels: ignite-3
>
> Currently a closure from {{runConsistently}} does not consider internal needs of an engine. For example, in {{aipersist}} checkpointer may already wait for {{writeLock}} acquisition, while "we" continue doing some work in our closure, stalling the entire system.
> We should provide an additional API to give users an option to stop the execution preemptively in case if engine needs resources, something like this:
> {code:java}
> interface Locker {
> ...
> boolean shouldRelease();
> ...
> } {code}
> I suggest not renaming the {{Locker}} class itself, that would bring too many unnecessary changes.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)