You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Kihwal Lee (JIRA)" <ji...@apache.org> on 2015/10/13 17:51:05 UTC

[jira] [Updated] (HDFS-8676) Delayed rolling upgrade finalization can cause heartbeat expiration and write failures

     [ https://issues.apache.org/jira/browse/HDFS-8676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kihwal Lee updated HDFS-8676:
-----------------------------
    Summary: Delayed rolling upgrade finalization can cause heartbeat expiration and write failures  (was: Delayed rolling upgrade finalization can cause heartbeat expiration)

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