[jira] [Commented] (HADOOP-13308) S3A delete and rename may fail to preserve parent directory.

["Steve Loughran (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HADOOP-13308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15344017#comment-15344017 ] 

Steve Loughran commented on HADOOP-13308:
-----------------------------------------

you could actually do the PUT without doing the check, couldn't you?

The biggest problem with having spurious parent dirs is that delete/ itself may do some checks for empty directories and handle them.

Maybe we need to think about some s3 fsck routine which does cleanup.

> 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
(v6.3.4#6332)

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