[
https://issues.apache.org/jira/browse/HDFS-5558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13831589#comment-13831589
]
Kihwal Lee commented on HDFS-5558:
----------------------------------
bq. I tried to reproduce the problem as mentioned with the help of test changes
in HDFS-5557, but could not get the Invalid Cast Exception in trunk code.
The test won't reproduce this issue because the client will lose every time.
In order to reproduce this, the client has to lose the race in HDFS-5557 for
the penultimate block and the datanode has to win the race for the last block.
I.e. produce block layout
[...][BlockInfoUnderConstruction:COMMITTED][BlockInfo:COMPLETE].
> LeaseManager monitor thread can crash if the last block is complete but
> another block is not.
> ---------------------------------------------------------------------------------------------
>
> Key: HDFS-5558
> URL: https://issues.apache.org/jira/browse/HDFS-5558
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 0.23.9, 2.3.0
> Reporter: Kihwal Lee
> Assignee: Kihwal Lee
> Attachments: HDFS-5558.branch-023.patch, HDFS-5558.patch
>
>
> As mentioned in HDFS-5557, if a file has its last and penultimate block not
> completed and the file is being closed, the last block may be completed but
> the penultimate one might not. If this condition lasts long and the file is
> abandoned, LeaseManager will try to recover the lease and the block. But
> {{internalReleaseLease()}} will fail with invalid cast exception with this
> kind of file.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
