[jira] [Updated] (HDDS-3152) Reduce number of chunkwriter threads in integration tests
[
https://issues.apache.org/jira/browse/HDDS-3152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham updated HDDS-3152:
-
Fix Version/s: 0.6.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Reduce number of chunkwriter threads in integration tests
> -
>
> Key: HDDS-3152
> URL: https://issues.apache.org/jira/browse/HDDS-3152
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Components: test
>Reporter: Attila Doroszlai
>Assignee: Attila Doroszlai
>Priority: Minor
> Labels: pull-request-available
> Fix For: 0.6.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Integration tests run multiple datanodes in the same JVM. Each datanode
> comes with 60 chunk writer threads by default (may be decreased in
> HDDS-3053). This makes thread dumps (eg. produced by
> {{GenericTestUtils.waitFor}} on timeout) really hard to navigate, as there
> may be 300+ such threads.
> Since integration tests are generally run with a single disk which is even
> shared among the datanodes, a few threads per datanode should be enough.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3152) Reduce number of chunkwriter threads in integration tests
[
https://issues.apache.org/jira/browse/HDDS-3152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Doroszlai updated HDDS-3152:
---
Status: Patch Available (was: In Progress)
> Reduce number of chunkwriter threads in integration tests
> -
>
> Key: HDDS-3152
> URL: https://issues.apache.org/jira/browse/HDDS-3152
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Components: test
>Reporter: Attila Doroszlai
>Assignee: Attila Doroszlai
>Priority: Minor
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Integration tests run multiple datanodes in the same JVM. Each datanode
> comes with 60 chunk writer threads by default (may be decreased in
> HDDS-3053). This makes thread dumps (eg. produced by
> {{GenericTestUtils.waitFor}} on timeout) really hard to navigate, as there
> may be 300+ such threads.
> Since integration tests are generally run with a single disk which is even
> shared among the datanodes, a few threads per datanode should be enough.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3152) Reduce number of chunkwriter threads in integration tests
[
https://issues.apache.org/jira/browse/HDDS-3152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-3152:
-
Labels: pull-request-available (was: )
> Reduce number of chunkwriter threads in integration tests
> -
>
> Key: HDDS-3152
> URL: https://issues.apache.org/jira/browse/HDDS-3152
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Components: test
>Reporter: Attila Doroszlai
>Assignee: Attila Doroszlai
>Priority: Minor
> Labels: pull-request-available
>
> Integration tests run multiple datanodes in the same JVM. Each datanode
> comes with 60 chunk writer threads by default (may be decreased in
> HDDS-3053). This makes thread dumps (eg. produced by
> {{GenericTestUtils.waitFor}} on timeout) really hard to navigate, as there
> may be 300+ such threads.
> Since integration tests are generally run with a single disk which is even
> shared among the datanodes, a few threads per datanode should be enough.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
