[
https://issues.apache.org/jira/browse/IGNITE-22217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin reassigned IGNITE-22217:
--------------------------------------------
Assignee: Alexander Lapin
> Meta storage idempotent invokes: implement idempotent cache cleanup logic
> -------------------------------------------------------------------------
>
> Key: IGNITE-22217
> URL: https://issues.apache.org/jira/browse/IGNITE-22217
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexander Lapin
> Assignee: Alexander Lapin
> Priority: Major
> Labels: ignite-3
>
> h3. Motivation
> General context is available in the IGNITE-21881. Specifics related to the
> idempotent cache persistency is covered in the IGNITE-22214. Given ticket is
> about removing obsolete cache entries from both volatile and persistent
> idempotent command caches.
> h3. Definition of Done
> * Obsolete idempotent cache entries are eventually removed from both
> volatile cache and meta storage persistent backup.
> h3. Implementation Notes
> There's no need to have command result longer than
> org.apache.ignite.internal.raft.configuration.RaftConfiguration#responseTimeout
> + CLOCK_SKEW. In future we may use MS GC in order to check aforementioned
> condition and asynchronously remove obsolete cache entries. For now we may
> use any other trigger, like some invoke calls.
> It's reasonable to remove persistent obsolete entry prior to removing
> corresponding entry from volatile cache for better robustness, thus we will
> only have entry in persistent storage if it's available in volatile one.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
