[HDFS-7073] Allow falling back to a non-SASL connection on DataTransferProtocol in several edge cases.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.6.0
• Component/s: datanode, hdfs-client, security
• Target Version/s: 2.6.0
• Hadoop Flags: Reviewed
• Assignee: Chris Nauroth
• Reporter: Chris Nauroth
• Created: 16/Sep/14 19:11
• Updated: 01/Dec/14 03:10
• Resolved: 20/Sep/14 05:17

Description

HDFS-2856 implemented general SASL support on DataTransferProtocol. Part of that work also included a fallback mode in case the remote cluster is running under a different configuration without SASL. I've discovered a few edge case configurations that this did not support:

• Cluster is unsecured, but has block access tokens enabled. This is not something I've seen done in practice, but I've heard historically it has been allowed. The HDFS-2856 code relied on seeing an empty block access token to trigger fallback, and this doesn't work if the unsecured cluster actually is using block access tokens.
• The DataNode has an unpublicized testing configuration property that could be used to skip the privileged port check. However, the HDFS-2856 code is still enforcing requirement of SASL when the ports are not privileged, so this would force existing configurations to make changes to activate SASL.

This patch will restore the old behavior so that these edge case configurations will continue to work the same way.

Issue Links

• breaks: HDFS-7107 Avoid Findbugs warning for synchronization on AbstractNNFailoverProxyProvider#fallbackToSimpleAuth.
• relates to: HDFS-2856 Fix block protocol so that Datanodes don't require root or jsvc