Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-11973

testAccountTxNodeRestart cause unexpected repairs in case of ReadRepair usage

    XMLWordPrintableJSON

Details

    • Task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None

    Description

      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.

      Attachments

        Issue Links

          is caused by

          Task - A task that needs to be done. IGNITE-10663 Implement cache mode allows reads with consistency check and fix

          • Major - Major loss of function.
          • Resolved
          links to

          Web Link Devlist discussion

          Web Link GitHub Pull Request #6679

          Activity

            People

              Unassigned Unassigned
              avinogradov Anton Vinogradov (Obsolete, actual is "av")
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 10m
                  10m