You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Rushabh S Shah (JIRA)" <ji...@apache.org> on 2017/02/22 19:09:44 UTC

[jira] [Created] (HADOOP-14104) Client should always ask namenode for kms provider path.

Rushabh S Shah created HADOOP-14104:
---------------------------------------

             Summary: 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: Bug
          Components: kms
            Reporter: Rushabh S Shah
            Assignee: Rushabh S Shah


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.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org