[
https://issues.apache.org/jira/browse/HDFS-15979?focusedWorklogId=585177&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-585177
]
ASF GitHub Bot logged work on HDFS-15979:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 19/Apr/21 14:46
Start Date: 19/Apr/21 14:46
Worklog Time Spent: 10m
Work Description: amahussein commented on pull request #2919:
URL: https://github.com/apache/hadoop/pull/2919#issuecomment-822525000
The failures are not related. Those were the intermittent failures reported
in the daily reports and existing jiras are addressing them.
> 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.
@jojochuang Do you have any feedback on those changes?
--
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: 585177)
Time Spent: 0.5h (was: 20m)
> 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
> Labels: pull-request-available
> Attachments: HDFS-15979.001.patch
>
> Time Spent: 0.5h
> 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
