Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 10 Aug 2017 19:49:02 +0000 (UTC)
From: "Lukas Majercak (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <JIRA.13093903.1502394534000.3218.1502394542288@Atlassian.JIRA>
In-Reply-To: <JIRA.13093903.1502394534000@Atlassian.JIRA>
References: <JIRA.13093903.1502394534000@Atlassian.JIRA> <JIRA.13093903.1502394534069@jira-lw-us.apache.org>
Subject: [jira] [Created] (HDFS-12288) Change DN xceiver count calculation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 10 Aug 2017 19:49:10 -0000

Lukas Majercak created HDFS-12288:
-------------------------------------

             Summary: Change DN xceiver count calculation
                 Key: HDFS-12288
                 URL: https://issues.apache.org/jira/browse/HDFS-12288
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: datanode, hdfs
            Reporter: Lukas Majercak
            Assignee: Lukas Majercak


The problem with the ThreadGroup.activeCount() method is that the method is only a very rough estimate, and in reality returns the total number of threads in the thread group as opposed to the threads actually running.

In some DNs, we saw this to return 50~ for a long time, even though the actual number of DataXceiver threads was next to none.
This is a big issue as we use the xceiverCount to make decisions on the NN for choosing replication source DN or returning DNs to clients for R/W.

The plan is to reuse the DataNodeMetrics.dataNodeActiveXceiversCount value which only accounts for actual number of DataXcevier threads currently running and thus represents the load on the DN much better.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org