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

Retry issues with background operations

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.2.0-incubating
    • 2.3.0
    • Framework
    • None

    Description

      Retry-able errors (CONNECTIONLOSS, OPERATIONTIMEOUT, SESSIONMOVED, SESSIONEXPIRED) are not propagated to callback when the retry policy gave up if the operation is done in background.

      Additionally, all background operations do not retry connection issues if the zookeeper connection is not currently connected. This is a major oversight.

      Attachments

        1. CURATOR-52.patch
          4 kB
          Michael Morello

        Issue Links

          blocks

          Bug - A problem which impairs or prevents the functions of the product. CURATOR-45 LeaderSelector threw exception, but still created ephemeral node, breaking everything

          • Major - Major loss of function.
          • Resolved
          is cloned by

          Bug - A problem which impairs or prevents the functions of the product. CURATOR-72 Background operations don't wait for connection timeout

          • Major - Major loss of function.
          • Resolved
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. CURATOR-673 Complete BackgroundCallback if curator got closed or exceptions from no-zookeeper world

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              randgalt Jordan Zimmerman
              barkbay Michael Morello
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: