Uploaded image for project: 'mod_cluster'
  1. mod_cluster
  2. MODCLUSTER-550

Failover targets should be chosen deterministically

    XMLWordPrintable

Details

    Description

      Under the following conditions:
      1. A request arrives for a session with an unknown route
      2. A request arrives for a session with a known route in an error state, or if the intended worker is unresponsive and needs to failover

      ... the failover target must be chosen in a deterministic way. This is meant to mitigate the situation where concurrent requests failover to different nodes and cause cluster-wide contention for the session. Given a consistent ordering of workers (e.g. lexographically), the failover target should be chosen by something like: hash code of session id % active worker count.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. UNDERTOW-898 Failover targets should be chosen deterministically

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-8550 Deterministic failover session owner issue

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. MODCLUSTER-557 Hot standby workers should be excluded from the deterministic failover candidate list

          • Critical - To be worked on immediately following BLOCKER issues.
          • Open

          Activity

            People

              pferraro@redhat.com Paul Ferraro
              pferraro@redhat.com Paul Ferraro
              Michal Karm Michal Karm
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: