You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Gabor Bota (Jira)" <ji...@apache.org> on 2020/02/13 17:37:00 UTC
[jira] [Commented] (HADOOP-16860) Prune -tombstones to remove
children entries
[ https://issues.apache.org/jira/browse/HADOOP-16860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036371#comment-17036371 ]
Gabor Bota commented on HADOOP-16860:
-------------------------------------
We don't remove directories during prune. However, there are orphan entries left somehow in ddb after some operation. This was a misunderstanding and should be solved elsehow.
> Prune -tombstones to remove children entries
> --------------------------------------------
>
> Key: HADOOP-16860
> URL: https://issues.apache.org/jira/browse/HADOOP-16860
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.3.0
> Reporter: Gabor Bota
> Assignee: Gabor Bota
> Priority: Major
>
> When you prune a directory in S3Guard the children entries are not pruned with the tombstoned parent (directory).
> I propose the solution to remove all children entries (the whole hierarchy) to avoid orphaned entries once the parent (directory) tombstone is removed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org