[
https://issues.apache.org/jira/browse/HDFS-5558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13836891#comment-13836891
]
Daryn Sharp commented on HDFS-5558:
-----------------------------------
+1 It sounds like you addressed Colin's concern. And yes, I helped debug a
case awhile back where the user accidentally set the block size to N-KB instead
of N-MB for their jobs. The NN was overwhelmed and the dfs client's request
for another block was being processed before the prior block's updates.
> 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.4.0
> Reporter: Kihwal Lee
> Assignee: Kihwal Lee
> Attachments: HDFS-5558.branch-023.patch, HDFS-5558.branch-023.patch,
> HDFS-5558.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)
