You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flume.apache.org by "Jarek Jarcec Cecho (JIRA)" <ji...@apache.org> on 2015/01/21 22:52:34 UTC

[jira] [Resolved] (FLUME-2594) Close Async HBase Client if there are large number of consecutive timeouts

     [ https://issues.apache.org/jira/browse/FLUME-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jarek Jarcec Cecho resolved FLUME-2594.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: v1.6.0

Thank you for the contribution [~hshreedharan]!

> 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)