[HADOOP-14104] Client should always ask namenode for kms provider path.

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.9.0, 3.0.0-alpha4, 2.8.2
• Component/s: kms
• Target Version/s: 2.8.1, 3.0.0-alpha4
• Assignee: Rushabh Shah
• Reporter: Rushabh Shah
• Created: 22/Feb/17 19:09
• Updated: 16/Aug/24 04:32
• Resolved: 06/Apr/17 21:40

Description

According to current implementation of kms provider in client conf, there can only be one kms.
In multi-cluster environment, if a client is reading encrypted data from multiple clusters it will only get kms token for local cluster.
Not sure whether the target version is correct or not.

Issue Links

• breaks: HDFS-13696 Distcp between 2 secure clusters and non encrypted zones fails with connection timeout
• breaks: HADOOP-14814 Fix incompatible API change on FsServerDefaults to HADOOP-14104
• breaks: HDFS-11689 New exception thrown by DFSClient#isHDFSEncryptionEnabled broke hacky hive code
• breaks: HDFS-11702 Remove indefinite caching of key provider uri in DFSClient
• is related to: HDDS-11227 Use OM's KMS from client side when connecting to a cluster and dealing with encrypted data
• is related to: HDFS-11687 Add new public encryption APIs required by Hive
• is related to: HIVE-16490 Hive should not use private HDFS APIs for encryption
• relates to: HDFS-13371 NPE for FsServerDefaults.getKeyProviderUri() for clientProtocol communication between 2.7 and 3.X
• relates to: HADOOP-16350 Ability to tell HDFS client not to request KMS Information from NameNode