Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-11398

RetryUpToMaximumTimeWithFixedSleep needs to behave more accurately

Add voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Patch Available
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None
    • None

    Description

      RetryUpToMaximumTimeWithFixedSleep now inherits RetryUpToMaximumCountWithFixedSleep and just acts as a wrapper to decide maxRetries. The current implementation uses (maxTime / sleepTime) as the number of maxRetries. This is fine if the actual for each retry is significantly less than the sleep time, but it becomes less accurate if each retry takes comparable amount of time as the sleep time. The problem gets worse when there are underlying retries.

      We may want to use timers inside RetryUpToMaximumTimeWithFixedSleep to perform accurate timing.

      Attachments

        1. HADOOP-11398.002.patch
          6 kB
          Akira Ajisaka
        2. HADOOP-11398.003.patch
          8 kB
          Akira Ajisaka
        3. HADOOP-11398-121114.patch
          6 kB
          Li Lu

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            gtcarrera9 Li Lu
            gtcarrera9 Li Lu

            Dates

              Created:
              Updated:

              Slack

                Issue deployment