[
https://issues.apache.org/jira/browse/FLUME-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14484177#comment-14484177
]
Hudson commented on FLUME-2654:
-------------------------------
UNSTABLE: Integrated in flume-trunk #727 (See
[https://builds.apache.org/job/flume-trunk/727/])
FLUME-2654. Clarify error message in MemoryChannel when byte capacity is
reached. (hshreedharan:
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=cfefda167ea42aa5d68e15ac55bc2d6394c2d48d)
* flume-ng-core/src/main/java/org/apache/flume/channel/MemoryChannel.java
> Memory channel error message related to byteCapacity needs refining
> -------------------------------------------------------------------
>
> Key: FLUME-2654
> URL: https://issues.apache.org/jira/browse/FLUME-2654
> Project: Flume
> Issue Type: Bug
> Reporter: Johny Rufus
> Assignee: Johny Rufus
> Priority: Minor
> Fix For: 1.6
>
> Attachments: FLUME-2654.patch
>
>
> Memory channel error message thrown in doCommit, when space runs out,
> mentions heap space as byteCapacity, but this value is not the actual heap
> capacity, as it goes through a set of transformations and gets divided by
> byteCapacitySlotSize
> So we need to refine the message a bit to reflect this, otherwise the user is
> mislead about the configured heap size
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
