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

Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2019/10/10 12:33:00 UTC

[jira] [Updated] (IGNITE-11973) testAccountTxNodeRestart cause unexpected repairs in case of ReadRepair usage

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

Maxim Muzafarov updated IGNITE-11973:
-------------------------------------
    Fix Version/s:     (was: 2.8)
                   2.9

> 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.9
>
>          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)