hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiao Chen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-11203) Rename support during re-encrypt EDEK
Date Fri, 28 Jul 2017 03:49:00 GMT

     [ https://issues.apache.org/jira/browse/HDFS-11203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Xiao Chen updated HDFS-11203:
-----------------------------
    Description: 
Currently HDFS-10899 disables renames within the EZ if it's under re-encryption. (similar
to current cross-zone rename checks).

We'd like to support rename in the long run, so cluster is fully functioning during re-encryption.

The reason rename is particularly difficult is:
- We want to re-encrypt all files under an EZ in one pass, without missing any
- We want to iterate through the files and keep track of where we are (i.e. a cursor), so
in case of NN failover/crash, we can resume from fsimage/edits.
- We cannot guarantee namespace is not changed during re-encryption. Newly created files automatically
has new edek, deleted files we don't care. But if a file is renamed from behind the cursor
to before, it may be missed in the re-encryption.

  was:
Currently HDFS-10899 disables renames within the EZ if it's under re-encryption. (similar
to current cross-zone rename checks).

We'd like to support rename in the long run, so cluster is fully functioning during re-encryption


> Rename support during re-encrypt EDEK
> -------------------------------------
>
>                 Key: HDFS-11203
>                 URL: https://issues.apache.org/jira/browse/HDFS-11203
>             Project: Hadoop HDFS
>          Issue Type: Task
>          Components: encryption
>            Reporter: Xiao Chen
>            Assignee: Xiao Chen
>
> Currently HDFS-10899 disables renames within the EZ if it's under re-encryption. (similar
to current cross-zone rename checks).
> We'd like to support rename in the long run, so cluster is fully functioning during re-encryption.
> The reason rename is particularly difficult is:
> - We want to re-encrypt all files under an EZ in one pass, without missing any
> - We want to iterate through the files and keep track of where we are (i.e. a cursor),
so in case of NN failover/crash, we can resume from fsimage/edits.
> - We cannot guarantee namespace is not changed during re-encryption. Newly created files
automatically has new edek, deleted files we don't care. But if a file is renamed from behind
the cursor to before, it may be missed in the re-encryption.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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


Mime
View raw message