[HDFS-4009] WebHdfsFileSystem and HftpFileSystem don't need delegation tokens

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Invalid
• Affects Version/s: 2.0.0-alpha
• Assignee: Karthik Kambatla
• Reporter: Thomas White
• Created: 26/Sep/12 15:06
• Updated: 03/Nov/14 18:05
• Resolved: 15/Nov/12 20:06

Description

Parent JIRA to track the work of removing delegation tokens from these filesystems.

This JIRA has evolved from the initial issue of these filesystems not stopping the DelegationTokenRenewer thread they were creating.

After further investigation, Daryn pointed out - "If you can get a token, you don't need a token"! Hence, these filesystems shouldn't use delegation tokens.

Evolution of the JIRA is listed below:
Update 2:
DelegationTokenRenewer is not required. The filesystems that are using it already have Krb tickets and do not need tokens. Remove DelegationTokenRenewer and all the related logic from WebHdfs and Hftp filesystems.

Update1:
DelegationTokenRenewer should be Singleton - the instance and renewer threads should be created/started lazily. The filesystems using the renewer shouldn't need to explicity start/stop the renewer, and only register/de-register for token renewal.

Initial issue:
HftpFileSystem and WebHdfsFileSystem should stop the DelegationTokenRenewer thread when they are closed.

Issue Links

• relates to: HADOOP-9049 DelegationTokenRenewer needs to be Singleton and FileSystems should register/deregister to/from.
• relates to: HADOOP-8891 Remove DelegationTokenRenewer and its logic from FileSystems using it

Sub-Tasks

• Remove unused TokenRenewer implementation from WebHdfsFileSystem and HftpFileSystem: Closed
• WebHdfsFileSystem shouldn't implicitly fetch delegation tokens: Resolved
• HftpFileSystem shouldn't implicity fetch delegation tokens: Resolved