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

Posted to issues@kudu.apache.org by "Will Berkeley (JIRA)" <ji...@apache.org> on 2017/10/02 19:09:00 UTC

[jira] [Resolved] (KUDU-2078) Flume sink fails to write if the size in bytes of the batch exceeds the client session's manual flush buffer size

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

Will Berkeley resolved KUDU-2078.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.5.0

Fixed in 2942760708d9bd252dc266434127d7eaa5107f55

> Flume sink fails to write if the size in bytes of the batch exceeds the client session's manual flush buffer size
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: KUDU-2078
>                 URL: https://issues.apache.org/jira/browse/KUDU-2078
>             Project: Kudu
>          Issue Type: Bug
>          Components: flume-sink
>    Affects Versions: 1.4.0
>            Reporter: Will Berkeley
>            Assignee: Will Berkeley
>             Fix For: 1.5.0
>
>
> The Flume sink uses MANUAL_FLUSH mode. If a set of operations is too large for the flush buffer, it will fail-- potentially over and over, if the channel supports retrying the transaction.
> We should be able to fix this by using AUTO_FLUSH_BACKGROUND, adjusting the buffer size, or returning a more useful error so that users can reconfigure their sink's batch size (though that size is in # of ops, not bytes).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)