[
https://issues.apache.org/jira/browse/IGNITE-11130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16756236#comment-16756236
]
Ignite TC Bot commented on IGNITE-11130:
----------------------------------------
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 7{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2952171]]
* IgniteCacheTestSuite7:
TxRollbackAsyncWithPersistenceTest.testSynchronousRollback - 0,0% fails in last
419 master runs.
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2952217&buildTypeId=IgniteTests24Java8_RunAll]
> 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
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)
