[
https://issues.apache.org/jira/browse/IGNITE-11130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-11130:
-----------------------------------------
Description:
The change introduced by IGNITE-7086 lead to the fact that
{{BackupPostProcessingClosure}} could attempt to store the initial value even
if the corresponding cache store is not configured.
For instance, transactional read operation where atomicity mode is OPTIMISTIC
and isolation level is SERIALIZABLE (native persistent enabled) tries to update
the local backup.
was:
The change introduced in IGNITE-7086 lead to the fact that
{{BackupPostProcessingClosure}} could attempt to store the initial value even
if the corresponding cache store is not configured.
For instance, transactional read operation where atomicity mode is OPTIMISTIC
and isolation level is SERIALIZABLE (native persistent enabled) tries to update
the local backup.
> BackupPostProcessingClosure should not save initial value on a backup node
> when cache store is not configured.
> --------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-11130
> URL: https://issues.apache.org/jira/browse/IGNITE-11130
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.7
> Reporter: Vyacheslav Koptilin
> Assignee: Vyacheslav Koptilin
> Priority: Major
> Fix For: 2.8
>
>
> The change introduced by IGNITE-7086 lead to the fact that
> {{BackupPostProcessingClosure}} could attempt to store the initial value even
> if the corresponding cache store is not configured.
> For instance, transactional read operation where atomicity mode is OPTIMISTIC
> and isolation level is SERIALIZABLE (native persistent enabled) tries to
> update the local backup.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
