Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-2445

Clean up client retry policies

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Critical
    • Resolution: Incomplete
    • None
    • None
    • Client

    Description

      Right now almost all retry behavior is governed by a single parameter that determines the number of retries. In a few places, there are also conf for the number of millis to sleep between retries. This isn't quite flexible enough. If we can refactor some of the retry logic into a RetryPolicy class, we could introduce exponential backoff where appropriate, clean up some of the config, etc

      Attachments

        Issue Links

          relates to

          New Feature - A new feature of the product, which has yet to be developed. HBASE-2937 Facilitate Timeouts In HBase Client

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. HBASE-5813 Retry immediately after a NotServingRegionException in a multiput

          • Major - Major loss of function.
          • Closed

          Activity

            People

              Unassigned Unassigned
              tlipcon Todd Lipcon
              Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: