[
https://issues.apache.org/jira/browse/HDFS-12163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsz Wo Nicholas Sze updated HDFS-12163:
---------------------------------------
Description:
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 a
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.
was:
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 a
1-datanode .
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.
> Ozone: MiniOzoneCluster uses 400+ threads
> -----------------------------------------
>
> Key: HDFS-12163
> URL: https://issues.apache.org/jira/browse/HDFS-12163
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ozone, test
> Reporter: Tsz Wo Nicholas Sze
>
> 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 a
> 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: [email protected]
For additional commands, e-mail: [email protected]
