Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Sun, 23 Feb 2014 16:51:21 +0000 (UTC)
From: "Arpit Agarwal (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12694372.1392070812432.89399.1393174281351@arcas>
In-Reply-To: <JIRA.12694372.1392070812432@arcas>
References: <JIRA.12694372.1392070812432@arcas>
Subject: [jira] [Updated] (HDFS-5922) DN heartbeat thread can get stuck in
 tight loop
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Arpit Agarwal updated HDFS-5922:
--------------------------------

    Attachment: HDFS-5922.02.patch

> DN heartbeat thread can get stuck in tight loop
> -----------------------------------------------
>
>                 Key: HDFS-5922
>                 URL: https://issues.apache.org/jira/browse/HDFS-5922
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode
>    Affects Versions: 2.3.0
>            Reporter: Aaron T. Myers
>            Assignee: Arpit Agarwal
>         Attachments: HDFS-5922.01.patch, HDFS-5922.02.patch
>
>
> We saw an issue recently on a test cluster where one of the DN threads was consuming 100% of a single CPU. Running jstack indicated that it was the DN heartbeat thread. I believe I've tracked down the cause to a bug in the accounting around the value of {{pendingReceivedRequests}}.
> More details in the first comment.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)