Details
Description
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.
Attachments
Attachments
Issue Links
- depends upon
-
HDFS-6618 FSNamesystem#delete drops the FSN lock between removing INodes from the tree and deleting them from the inode map
- Closed