[
https://issues.apache.org/jira/browse/HDFS-6951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14124443#comment-14124443
]
Hadoop QA commented on HDFS-6951:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12667002/HDFS-6951.006.patch
against trunk revision 3b35f81.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/7929//console
This message is automatically generated.
> Saving namespace and restarting NameNode will remove existing encryption zones
> ------------------------------------------------------------------------------
>
> Key: HDFS-6951
> URL: https://issues.apache.org/jira/browse/HDFS-6951
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: encryption
> Affects Versions: 3.0.0
> Reporter: Stephen Chu
> Assignee: Charles Lamb
> Attachments: HDFS-6951-prelim.002.patch, HDFS-6951-testrepo.patch,
> HDFS-6951.001.patch, HDFS-6951.002.patch, HDFS-6951.003.patch,
> HDFS-6951.004.patch, HDFS-6951.005.patch, HDFS-6951.006.patch, editsStored
>
>
> Currently, when users save namespace and restart the NameNode, pre-existing
> encryption zones will be wiped out.
> I could reproduce this on a pseudo-distributed cluster:
> * Create an encryption zone
> * List encryption zones and verify the newly created zone is present
> * Save the namespace
> * Kill and restart the NameNode
> * List the encryption zones and you'll find the encryption zone is missing
> I've attached a test case for {{TestEncryptionZones}} that reproduces this as
> well. Removing the saveNamespace call will get the test to pass.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
