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

Merge: make the coordinator remain the same if possible after a merge

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Duplicate
    • Major
    • 3.2
    • None
    • None

    Description

      When we have

      {C, A, B}

      and split into

      {C,A}

      and

      {B}

      , then a merge will produce

      {A,B,C}

      . Therefore the coord is moved from C to A. For certain apps, e.g. JBoss singletons, this is not good, as we're moving the singleton services from a perfectly healthy node to a different node.
      GOAL: come up with a deterministic policy of picking a coord such that we minimize coord switching if the existing coord is still member of the cluster.
      This depends on or is related to the flexible coord pick policy JIRA issue

      Attachments

        Issue Links

          is related to

          Feature Request - Feature requests from customers and/or users JGRP-592 Pluggable policy for picking coordinator

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved

          Activity

            Public project attachment banner

              context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
              current Project key: JGRP

              People

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

                Dates

                  Created:
                  Updated:
                  Resolved: