Uploaded image for project: 'JGroups'
  1. JGroups
  2. JGRP-1061

FLUSH: asymmetric merge fails

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 2.10
    • None
    • None

      A:

      {B,A,C}
      B: {B,C}
      C: {B,C}

      B and C have the same view, but A has a different (older) view which still includes B and C

      The new merge now determines that the partition coordinators for the merge are B and A.

      When FLUSH is enabled, before handling the merge request A tries to flush {A,B,C} and B tries to flush {B,C}. The latter works, but the former fails as A cannot communicate with B and C !

      SOLUTION: the partition for A needs to be {A} and not {B,A,C}

      .

      Is this possible in all cases, or can we NOT prevent merging of overlapping partitions ? (Then flush would always fail !)

            rhn-engineering-bban Bela Ban
            rhn-engineering-bban Bela Ban
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: