[
https://issues.apache.org/jira/browse/HADOOP-13308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16360683#comment-16360683
]
Steve Loughran commented on HADOOP-13308:
-----------------------------------------
I think we may just have to accept that this can happen, though I doubt s3guard
will be happy; it's fsck may need to catch up with reality
> S3A delete and rename may fail to preserve parent directory.
> ------------------------------------------------------------
>
> Key: HADOOP-13308
> URL: https://issues.apache.org/jira/browse/HADOOP-13308
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Reporter: Chris Nauroth
> Priority: Minor
>
> When a file or directory is deleted or renamed in S3A, and the result of that
> operation makes the parent empty, S3A must store a fake directory (a pure
> metadata object) at the parent to indicate that the directory still exists.
> The logic for restoring fake directories is not resilient to a process death.
> This may cause a directory to vanish unexpectedly after a deletion or rename
> of its last child.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
