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

Alexander Lapin updated IGNITE-22217:
-------------------------------------
    Description: 
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

 

 

  was:
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

 


> 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
>            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
>  
>  



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

Reply via email to