hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinay (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5558) LeaseManager monitor thread can crash if the last block is complete but another block is not.
Date Mon, 25 Nov 2013 09:02:38 GMT

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

Vinay commented on HDFS-5558:
-----------------------------

HDFS-4882 is more related to {{dfs.namenode.replication.min=2}} which is not taking care of
adding extra datanode during PIPELINE_CLOSE_RECOVERY, 

I agree, not adding extra datanodes can cause {{checkLeases()}} into infiniate loop, but with
the fix given in this jira that situation may not come. 
Now client's close() have timeout and fails after timeout.

> 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)

Mime
View raw message