[
https://issues.apache.org/jira/browse/FLUME-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248140#comment-13248140
]
Juhani Connolly commented on FLUME-1011:
----------------------------------------
Since no-one seemed to be working on this, I put together a basic patch that
addresses the core issue of potentially spawning too many threads.
If the core thread pool size needs to be configured too, maybe that could be
turned into a separate issue?
> AvroSource should have a configurable max thread count
> ------------------------------------------------------
>
> Key: FLUME-1011
> URL: https://issues.apache.org/jira/browse/FLUME-1011
> Project: Flume
> Issue Type: Improvement
> Affects Versions: v1.0.0
> Reporter: Mike Percy
> Fix For: v1.2.0
>
>
> AvroSource via NettyServer uses Executors.newCachedThreadPool() when
> accepting incoming connections, which means that there is no upper limit on
> the number of threads that can be spawned. It would be good to expose
> configurable core & max thread pool sizes and provide some sane defaults to
> avoid OutOfMemory errors.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
