[
https://issues.apache.org/jira/browse/FLUME-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14286462#comment-14286462
]
Hudson commented on FLUME-2594:
-------------------------------
SUCCESS: Integrated in flume-trunk #708 (See
[https://builds.apache.org/job/flume-trunk/708/])
FLUME-2594: Close Async HBase Client if there are large number of consecutive
timeouts (jarcec:
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=82631f811a7c6a4d8e6ec886f80d1a21876947e5)
*
flume-ng-sinks/flume-ng-hbase-sink/src/main/java/org/apache/flume/sink/hbase/AsyncHBaseSink.java
> Close Async HBase Client if there are large number of consecutive timeouts
> --------------------------------------------------------------------------
>
> Key: FLUME-2594
> URL: https://issues.apache.org/jira/browse/FLUME-2594
> Project: Flume
> Issue Type: Bug
> Reporter: Hari Shreedharan
> Assignee: Hari Shreedharan
> Fix For: v1.6.0
>
> Attachments: FLUME-2594.patch
>
>
> A large number of timeouts can lead to several thousands of messages being
> buffered but never removed from the HBaseClient's buffers. This can cause a
> major heap spike. So we should close and dereference the HBaseClient if we
> hit many failures from the HBase side to clear up the buffers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
