hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sangjin Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8676) Delayed rolling upgrade finalization can cause heartbeat expiration and write failures
Date Fri, 20 Nov 2015 23:58:11 GMT

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

Sangjin Lee commented on HDFS-8676:
-----------------------------------

Does this issue exist in 2.6.x? Should this be backported to branch-2.6?

> Delayed rolling upgrade finalization can cause heartbeat expiration and write failures
> --------------------------------------------------------------------------------------
>
>                 Key: HDFS-8676
>                 URL: https://issues.apache.org/jira/browse/HDFS-8676
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Kihwal Lee
>            Assignee: Walter Su
>            Priority: Critical
>             Fix For: 3.0.0, 2.7.2
>
>         Attachments: HDFS-8676.01.patch, HDFS-8676.02.patch
>
>
> In big busy clusters where the deletion rate is also high, a lot of blocks can pile up
in the datanode trash directories until an upgrade is finalized.  When it is finally finalized,
the deletion of trash is done in the service actor thread's context synchronously.  This blocks
the heartbeat and can cause heartbeat expiration.  
> We have seen a namenode losing hundreds of nodes after a delayed upgrade finalization.
 The deletion of trash directories should be made asynchronous.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message