You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Nikolay Izhikov (Jira)" <ji...@apache.org> on 2023/03/15 15:40:00 UTC

[jira] [Updated] (IGNITE-19020) Expire time not written on transaction commit

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

Nikolay Izhikov updated IGNITE-19020:
-------------------------------------
    Description: 
In case usage of putAllConflict, expireTime behaviour differs from standart cache operations.
We must allow to the plugin providers to specify expiryTime when resolving entries conflicts.

  was:{{GridDistributedTxRemoteAdapter#commitIfLocked}} set DataEntry#expireTime = 0 even if expireTime explicitly set. This leads to CDC issues and possible consistency issues on node failover.


> Expire time not written on transaction commit
> ---------------------------------------------
>
>                 Key: IGNITE-19020
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19020
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Nikolay Izhikov
>            Assignee: Nikolay Izhikov
>            Priority: Major
>              Labels: IEP-59, ise
>             Fix For: 2.15
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> In case usage of putAllConflict, expireTime behaviour differs from standart cache operations.
> We must allow to the plugin providers to specify expiryTime when resolving entries conflicts.



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