Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 48348200CEC for ; Tue, 1 Aug 2017 07:26:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 467B116664B; Tue, 1 Aug 2017 05:26:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 9228B166614 for ; Tue, 1 Aug 2017 07:26:04 +0200 (CEST) Received: (qmail 62890 invoked by uid 500); 1 Aug 2017 05:26:03 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 62872 invoked by uid 99); 1 Aug 2017 05:26:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Aug 2017 05:26:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 35995C036C for ; Tue, 1 Aug 2017 05:26:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id Y8SZkL0Zd1yo for ; Tue, 1 Aug 2017 05:26:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id C84D35F476 for ; Tue, 1 Aug 2017 05:26:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id D64E3E0A64 for ; Tue, 1 Aug 2017 05:26:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 30D822464E for ; Tue, 1 Aug 2017 05:26:00 +0000 (UTC) Date: Tue, 1 Aug 2017 05:26:00 +0000 (UTC) From: "Weiwei Yang (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-12163) Ozone: MiniOzoneCluster uses 400+ threads MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 01 Aug 2017 05:26:05 -0000 [ https://issues.apache.org/jira/browse/HDFS-12163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16108392#comment-16108392 ] Weiwei Yang commented on HDFS-12163: ------------------------------------ Hi [~anu] Here is the result after set 20 handler for KSM, | (distributed,1) | init | 6 | | (distributed,1) | MiniOzoneCluster | 222 | | (distributed,1) | shutdown | 80 | | (distributed,1) | sleep | 13 | I will overwrite this value to 20 in {{MiniOzoneCluster}} since 200 is not necessary for testing. > Ozone: MiniOzoneCluster uses 400+ threads > ----------------------------------------- > > Key: HDFS-12163 > URL: https://issues.apache.org/jira/browse/HDFS-12163 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ozone, test > Reporter: Tsz Wo Nicholas Sze > Assignee: Weiwei Yang > Attachments: most_used_threads.png, TestOzoneThreadCount20170719.patch, thread_dump.png > > > Checked the number of active threads used in MiniOzoneCluster with various settings: > - Local handlers > - Distributed handlers > - Ratis-Netty > - Ratis-gRPC > The results are similar for all the settings. It uses 400+ threads for an 1-datanode MiniOzoneCluster. > Moreover, there is a thread leak -- a number of the threads do not shutdown after the test is finished. Therefore, when tests run consecutively, the later tests use more threads. > Will post the details in comments. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org