[
https://issues.apache.org/jira/browse/HDFS-4516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13607312#comment-13607312
]
Uma Maheswara Rao G commented on HDFS-4516:
-------------------------------------------
I think directly depending on fsync call after creatBlockOutStream also will
have one issue.
Suppose, if createBlockOutPutStream sucess and trying to call fsync, at the
same time active NN failed and standyb becomes active. In this case, fsync call
will end up persisting empty blocks details and there won't be any block
collection in new Namenode related to file. When DNs reporting that created
blocks, they will be invalidated saying there are no stored block available
with it.
> Client crash after block allocation and NN switch before lease recovery for
> the same file can cause readers to fail forever
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-4516
> URL: https://issues.apache.org/jira/browse/HDFS-4516
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 3.0.0, 2.0.3-alpha
> Reporter: Uma Maheswara Rao G
> Priority: Critical
>
> If client crashes just after allocating block( blocks not yet created in DNs)
> and NN also switched after this, then new Namenode will not know about locs.
> Further details will be in comment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
