[
https://issues.apache.org/jira/browse/FLUME-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13250365#comment-13250365
]
Hudson commented on FLUME-1011:
-------------------------------
Integrated in flume-trunk #167 (See
[https://builds.apache.org/job/flume-trunk/167/])
FLUME-1011: AvroSource should have a configurable max thread count
(Juhani Connolly via Brock Noland) (Revision 1311535)
Result = SUCCESS
brock : http://svn.apache.org/viewvc/?view=rev&rev=1311535
Files :
*
/incubator/flume/trunk/flume-ng-core/src/main/java/org/apache/flume/source/AvroSource.java
*
/incubator/flume/trunk/flume-ng-core/src/test/java/org/apache/flume/source/TestAvroSource.java
> 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
> Assignee: Juhani Connolly
> Fix For: v1.2.0
>
> Attachments: FLUME-1011.2.patch
>
>
> 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
