[
https://issues.apache.org/jira/browse/IGNITE-8791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Kovalenko updated IGNITE-8791:
------------------------------------
Description:
When we commit transaction from primary to backup, we don't assign
updateCounter to WAL DataRecord /Entry associated with TxEntry, altough
increment updateCounter in backup partition correctly.
After that we have DataRecord's with zero update counters in WAL on backup
node. This leads to WAL rebalance errors if we start suppliying process from
such node partition.
We should save actual updateCounter to WAL even in case commiting to backup
and introduce tests for Tx Cache WAL rebalancing.
was:
{noformat}
junit.framework.AssertionFailedError: 46 8204 expected:<TestValue{v1=103015623,
v2=2139634319}> but was:<TestValue{v1=-1755545912, v2=-1123060388}>
{noformat}
> Missed updateCounter in WAL DataRecord when commit transaction from primary
> to backup
> -------------------------------------------------------------------------------------
>
> Key: IGNITE-8791
> URL: https://issues.apache.org/jira/browse/IGNITE-8791
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.5
> Reporter: Pavel Kovalenko
> Assignee: Pavel Kovalenko
> Priority: Major
> Fix For: 2.7
>
>
> When we commit transaction from primary to backup, we don't assign
> updateCounter to WAL DataRecord /Entry associated with TxEntry, altough
> increment updateCounter in backup partition correctly.
> After that we have DataRecord's with zero update counters in WAL on backup
> node. This leads to WAL rebalance errors if we start suppliying process from
> such node partition.
> We should save actual updateCounter to WAL even in case commiting to backup
> and introduce tests for Tx Cache WAL rebalancing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
