Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-21236

Inconsistent topology after coordinator leaving when using TCP transport-based failure detection mechanism

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • 40.0.0.Beta1, 39.0.1.Final
    • 37.0.0.Final, 37.0.1.Final, 38.0.0.Final, 38.0.1.Final, 39.0.0.Beta1
    • Clustering
    • None
    • Hide

      git revert abc04366d9b686b5c9d541682dee91642b5508a8

      Show
      git revert abc04366d9b686b5c9d541682dee91642b5508a8
    • Workaround Exists
    • Hide

      Add FD_SOCK2 to the stack.

      Show
      Add FD_SOCK2 to the stack.
    • ---
    • ---

      We observed this in WFLY-21180 after enabling transport-based FD and removing FD_SOCK2 from the stack.

      Reference to JGroups branch we use - https://github.com/belaban/JGroups/commits/5.5.x (was 5.4.x at the time of filing, but we can still reproduce this with 5.5)

      Change for this with the jgroups component upgrade will need to revert those changes (https://github.com/wildfly/wildfly/commit/abc04366d9b686b5c9d541682dee91642b5508a8).

              rhn-engineering-rhusar Radoslav Husar
              rhn-engineering-rhusar Radoslav Husar
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: