[
https://issues.apache.org/jira/browse/IGNITE-11973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16948540#comment-16948540
]
Maxim Muzafarov commented on IGNITE-11973:
------------------------------------------
Moved to the next release due to inactivity. Please, feel free to move it back
if you will be able to complete the ticket by 2.8 code freeze date, December 2,
2019.
> testAccountTxNodeRestart cause unexpected repairs in case of ReadRepair usage
> -----------------------------------------------------------------------------
>
> Key: IGNITE-11973
> URL: https://issues.apache.org/jira/browse/IGNITE-11973
> Project: Ignite
> Issue Type: Task
> Reporter: Anton Vinogradov
> Assignee: Anton Vinogradov
> Priority: Major
> Labels: iep-31
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Just add withReadRepair() proxy to test's cache and you'll see unexpected
> data repairs (values are differ on backups while primary is locked).
> To debug this add a breakpoint to
> {{GridNearReadRepairFuture#recordConsistencyViolation}} after
> fixedRaw.isEmpty() check.
> Not empty map means repair happened.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
