Uploaded image for project: 'Apache Curator'
  1. Apache Curator
  2. CURATOR-8

Possible mishandling of connection timeouts on large/shooty clusters

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.0-incubating
    • Fix Version/s: 2.3.0
    • Component/s: Client
    • Labels:
      None

      Description

      See CURATOR-7 for background.

      ConnectionState.checkTimeouts resets the connection if the session timeout has expired, whether or not we ever had a session. If one has a large, shooty cluster with a short session timeout and a long connection timeout, this might reset the host list pointer to zero every sessionTimeoutMs, never letting it connect to a valid, available host towards the end of the list. On the other hand, if it is an assertion that sessionTimeout > connectionTimeout always, then the min() call is not required and the ifelse should read "else if (elapsed > connectionTimeoutMs)" instead of just "else".

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                randgalt Jordan Zimmerman
                Reporter:
                arren Shevek
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: