Details

    • Type: Bug
    • Status: New (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 11.0.0.Dev04, 10.1.6.Final
    • Fix Version/s: None
    • Component/s: Core, State Transfer
    • Labels:
      None

      Description

      DefaultConflictManager.cancelConflictResolution() has no effect, because it completes a CompletableFuture but it does not actually stop the iteration over conflicts.

      Luckily it's only used when the cache is down to a single node, which would make the conflict resolution much faster anyway, so it's not critical.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                dan.berindei Dan Berindei
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: