[HDFS-4805] Webhdfs client is fragile to token renewal errors

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.23.0, 2.0.0-alpha, 3.0.0-alpha1
• Fix Version/s: 2.1.0-beta
• Component/s: webhdfs
• Target Version/s: 2.1.0-beta, 0.23.8
• Hadoop Flags: Reviewed
• Assignee: Daryn Sharp
• Reporter: Daryn Sharp
• Created: 07/May/13 17:31
• Updated: 12/May/16 18:12
• Resolved: 20/May/13 16:22

Description

Webhdfs internally acquires a token that will be used for DN-based operations. The token renewer in common will try to renew that token. If a renewal fails for any reason, it will try to get another token. If that fails, it gives up and the token webhdfs holds will soon expire.

A transient network outage or a restart of the NN may cause webhdfs to be left holding an expired token, effectively rendering webhdfs useless. This is fatal for daemons.