[HADOOP-11398] RetryUpToMaximumTimeWithFixedSleep needs to behave more accurately

• Type: Bug
• Status: Patch Available
• Priority: Major
• Resolution: Unresolved
• Assignee: Li Lu
• Reporter: Li Lu
• Created: 11/Dec/14 22:07
• Updated: 05/Sep/17 17:10

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.

Issue Links

• is duplicated by: HADOOP-14828 RetryUpToMaximumTimeWithFixedSleep is not bounded by maximum time
• is duplicated by: YARN-3364 Clarify Naming of yarn.client.nodemanager-connect.max-wait-ms and yarn.resourcemanager.connect.max-wait.ms
• relates to: YARN-3554 Default value for maximum nodemanager connect wait time is too high