[
https://issues.apache.org/jira/browse/HDFS-7241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charles Lamb resolved HDFS-7241.
--------------------------------
Resolution: Not a Problem
Assignee: Charles Lamb
Since creating an encryption zone is an administrative function, it makes the
most sense to just create it on the underlying HDFS namenode rather than
through viewfs.
> Unable to create encryption zone for viewfs:// after namenode federation is
> enabled
> -----------------------------------------------------------------------------------
>
> Key: HDFS-7241
> URL: https://issues.apache.org/jira/browse/HDFS-7241
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: encryption, federation
> Affects Versions: fs-encryption (HADOOP-10150 and HDFS-6134)
> Reporter: Xiaomin Zhang
> Assignee: Charles Lamb
>
> After configuring namenode federation for the cluster, I also enabled client
> mount table and viewfs as default URI. The hdfs crypto commands now failed
> with below error:
> # hdfs crypto -createZone -keyName key1 -path /user/test
> IllegalArgumentException: FileSystem viewfs://cluster18/ is not an HDFS file
> system
> This blocks the whole encryption at-rest feature as no zone could be defined
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
