[ 
https://issues.apache.org/jira/browse/HDFS-15979?focusedWorklogId=584239&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-584239
 ]

ASF GitHub Bot logged work on HDFS-15979:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 16/Apr/21 12:15
            Start Date: 16/Apr/21 12:15
    Worklog Time Spent: 10m 
      Work Description: amahussein opened a new pull request #2919:
URL: https://github.com/apache/hadoop/pull/2919


   [HDFS-15979](https://issues.apache.org/jira/browse/HDFS-15979) Move within 
EZ fails and cannot remove nested EZs
   
   The test failures are not related to the changes. Those three tests have 
related opened Jiras and they were failing for some time.
   The changes were contributed by @daryn-sharp and we have our internal 
clusters running on those changes with hadoop-2.8 and hadoop-2.10.
   I made some modifications in order to handle the conflict since our internal 
branch has a feature that is not merged yet into the community (HDFS-13009).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 584239)
    Remaining Estimate: 0h
            Time Spent: 10m

> Move within EZ fails and cannot remove nested EZs
> -------------------------------------------------
>
>                 Key: HDFS-15979
>                 URL: https://issues.apache.org/jira/browse/HDFS-15979
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: encryption, hdfs
>            Reporter: Ahmed Hussein
>            Assignee: Ahmed Hussein
>            Priority: Major
>         Attachments: HDFS-15979.001.patch
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Moving between EZ directories should work fine if the EZ key for the 
> directories is identical. If the key is name identical then no 
> decrypt/re-encrypt is necessary.
> However, the rename operation checks more than the key name. It compares the 
> inode number (unique identifier) of the source and dest dirs which will never 
> be the same for 2 dirs resulting in the cited failure. Note it also 
> incorrectly compares the key version.
> A related issue is if an ancestor of a EZ share the same key (ie. 
> /projects/foo and /projects/foo/bar/blah both use same key), files also 
> cannot be moved from the child to a parent dir, plus the child EZ cannot be 
> removed even though it's now covered by the ancestor.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to