[ https://issues.apache.org/jira/browse/HADOOP-14104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rushabh S Shah updated HADOOP-14104: ------------------------------------ Attachment: HADOOP-14104-trunk-v4.patch Addressed some of the checkstyle comments. Since the config key name "CommonConfigurationKeysPublic.HADOOP_SECURITY_KEY_PROVIDER_PATH" is so big, it can't fit in a line within 80 characters and remaining are not added by this patch. Test failures: 1. TestWebHdfsTimeouts - Fails consistently with and without the patch. Tracked via HDFS-11043 2. TestDataNodeVolumeFailureReporting - Passes locally on my box. Ran multiple times. Seems like a flaky test. 3. TestDFSZKFailoverController - Passes locally on my box. Proven to be a flaky test. We tried to fix it via HDFS-9333 but still failing. Left a comment on HDFS-9333. > Client should always ask namenode for kms provider path. > -------------------------------------------------------- > > Key: HADOOP-14104 > URL: https://issues.apache.org/jira/browse/HADOOP-14104 > Project: Hadoop Common > Issue Type: Improvement > Components: kms > Reporter: Rushabh S Shah > Assignee: Rushabh S Shah > Attachments: HADOOP-14104-trunk.patch, HADOOP-14104-trunk-v1.patch, > HADOOP-14104-trunk-v2.patch, HADOOP-14104-trunk-v3.patch, > HADOOP-14104-trunk-v4.patch > > > 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. -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org