Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Wed, 8 Apr 2015 22:51:12 +0000 (UTC)
From: "Andrew Wang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12771798.1422902603000.33014.1428533472426@Atlassian.JIRA>
In-Reply-To: <JIRA.12771798.1422902603000@Atlassian.JIRA>
References: <JIRA.12771798.1422902603000@Atlassian.JIRA>
 <JIRA.12771798.1422902603447@arcas>
Subject: [jira] [Commented] (HDFS-7725) Incorrect "nodes in service" metrics
 caused all writes to fail
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrew Wang commented on HDFS-7725:
-----------------------------------

Hi Ming, the latest looks good to me. +1 will commit shortly.

Kihwal, I looked quickly and I don't think this will change getMaxNodesPerRack behavior. This fixes up the live/dead node counts kept in the heartbeat manager, and I don't think those counts are used by getMaxNodesPerRack.

> Incorrect "nodes in service" metrics caused all writes to fail
> --------------------------------------------------------------
>
>                 Key: HDFS-7725
>                 URL: https://issues.apache.org/jira/browse/HDFS-7725
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Ming Ma
>            Assignee: Ming Ma
>         Attachments: HDFS-7725-2.patch, HDFS-7725-3.patch, HDFS-7725.patch
>
>
> One of our clusters sometimes couldn't allocate blocks from any DNs. BlockPlacementPolicyDefault complains with the following messages for all DNs.
> {noformat}
> the node is too busy (load:x > y)
> {noformat}
> It turns out the {{HeartbeatManager}}'s {{nodesInService}} was computed incorrectly when admins decomm or recomm dead nodes. Here are two scenarios.
> * Decomm dead nodes. It turns out HDFS-7374 has fixed it; not sure if it is intentional. cc / [~zhz], [~andrew.wang], [~atm] Here is the sequence of event without HDFS-7374.
> ** Cluster has one live node. nodesInService == 1
> ** The node becomes dead. nodesInService == 0
> ** Decomm the node. nodesInService == -1
> * However, HDFS-7374 introduces another inconsistency when recomm is involved.
> ** Cluster has one live node. nodesInService == 1
> ** The node becomes dead. nodesInService == 0
> ** Decomm the node. nodesInService == 0
> ** Recomm the node. nodesInService == 1


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