[
https://issues.apache.org/jira/browse/OOZIE-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Bacsko updated OOZIE-2736:
--------------------------------
Description:
Currently we have a lots of threads during test execution. On one hand, this is
understandable because we start an entire YARN cluster with all the services
inside a single JVM. Still, the number of threads can be reduced. By default,
certain properties are not set which causes almost all thread pools to start
with 50 threads, which is an unnecessarily high number.
The problem is that every thread consumes memory even if it doesn't run
anything. A more noticeable downside is that retrieving a thread dump results
in a large output from jstack.
was:
Currently we have a lots of threads during test execution. On one hand, this is
understandable because we start an entire YARN cluster with all the services
inside a single JVM. Still, the number of threads can be reduced. By default,
certain properties are not set which causes almost all thread pools to start
with 50 threads, which is an unnecessarily high number.
The problem is that every thread consumes memory even if it doesn't run
anything, so on a re. A more noticeable downside is that retrieving a thread
dump results in a large output from jstack.
> Reduce the number of threads during test execution
> --------------------------------------------------
>
> Key: OOZIE-2736
> URL: https://issues.apache.org/jira/browse/OOZIE-2736
> Project: Oozie
> Issue Type: Improvement
> Reporter: Peter Bacsko
> Assignee: Peter Bacsko
> Attachments: OOZIE-2736-001.patch, OOZIE-2736-002.patch
>
>
> Currently we have a lots of threads during test execution. On one hand, this
> is understandable because we start an entire YARN cluster with all the
> services inside a single JVM. Still, the number of threads can be reduced. By
> default, certain properties are not set which causes almost all thread pools
> to start with 50 threads, which is an unnecessarily high number.
> The problem is that every thread consumes memory even if it doesn't run
> anything. A more noticeable downside is that retrieving a thread dump results
> in a large output from jstack.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
