[
https://issues.apache.org/jira/browse/FLUME-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470858#comment-13470858
]
Hudson commented on FLUME-1535:
-------------------------------
Integrated in flume-trunk #312 (See
[https://builds.apache.org/job/flume-trunk/312/])
FLUME-1535. Ability to specify the capacity of MemoryChannel in bytes.
(Revision 246c1b0213a2089e6cb684d1d982cd03015fb09e)
Result = SUCCESS
hshreedharan :
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=246c1b0213a2089e6cb684d1d982cd03015fb09e
Files :
* flume-ng-core/src/main/java/org/apache/flume/channel/MemoryChannel.java
* flume-ng-core/src/test/java/org/apache/flume/channel/TestMemoryChannel.java
> Ability to specify the capacity of MemoryChannel in bytes
> ---------------------------------------------------------
>
> Key: FLUME-1535
> URL: https://issues.apache.org/jira/browse/FLUME-1535
> Project: Flume
> Issue Type: Improvement
> Components: Channel
> Affects Versions: v1.2.0
> Reporter: Jayant Shekhar
> Assignee: Ted Malaska
> Labels: patch
> Fix For: v1.3.0
>
> Attachments: FLUME-1535-0.patch, FLUME-1535-1.patch,
> FLUME-1535-4.patch, FLUME-1535-5-Atomic.patch, FLUME-1535-Semaphore-0.patch,
> FLUME-1535-Semaphore-1.patch, FLUME-1535-Semaphore-3.patch
>
>
> Users should be able to specify the capacity of memory channel in bytes.
> Currently users are able to specify the capacity in terms of max number of
> events. This causes issues when the size of the events can vary significantly
> (a couple of KB to MB) and could easily result in the Flume agent running
> into OOM.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
