[
https://issues.apache.org/jira/browse/HDFS-12163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16109349#comment-16109349
]
Anu Engineer commented on HDFS-12163:
-------------------------------------
Not sure if we need all the other changes too for the thread count to come
down, or only setting handlers to 20 is needed. I suggest that we make this
change via the builder pattern we have instead of the Debugging patch you have.
So some tests are able to change the miniOzoneCluster KSM handler count.
Or you can check if the thread count is set to a default value and if so, set
them to 20. Either one works.
Conceptually, I am +1 on this change. Thanks for finding and fixing it.
> 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: HDFS-12163-HDFS-7240.001.patch, 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
