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

Aaron T. Myers commented on HDFS-6647:
--------------------------------------

bq. It does. But I think closing the file in this case is a bit complicated. I 
can think of many corner cases. The snapshot experts should chime in.

Yea, I figured that'd be more complex. Totally fine to punt on that for now.

Thanks, Kihwal.

> Edit log corruption when pipeline recovery occurs for deleted file present in 
> snapshot
> --------------------------------------------------------------------------------------
>
>                 Key: HDFS-6647
>                 URL: https://issues.apache.org/jira/browse/HDFS-6647
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode, snapshots
>    Affects Versions: 2.4.1
>            Reporter: Aaron T. Myers
>            Assignee: Kihwal Lee
>            Priority: Blocker
>         Attachments: HDFS-6647-failing-test.patch, HDFS-6647.patch
>
>
> I've encountered a situation wherein an OP_UPDATE_BLOCKS can appear in the 
> edit log for a file after an OP_DELETE has previously been logged for that 
> file. Such an edit log sequence cannot then be successfully read by the 
> NameNode.
> More details in the first comment.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to