You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2016/11/28 21:49:00 UTC

[jira] [Assigned] (KUDU-1752) C++ client error memory should be bounded

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

Todd Lipcon reassigned KUDU-1752:
---------------------------------

    Assignee: Alexey Serbin

Alexey mentioned offline that he'd look at this

> C++ client error memory should be bounded
> -----------------------------------------
>
>                 Key: KUDU-1752
>                 URL: https://issues.apache.org/jira/browse/KUDU-1752
>             Project: Kudu
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.0.0
>            Reporter: Matthew Jacobs
>            Assignee: Alexey Serbin
>            Priority: Critical
>              Labels: client, impala
>
> The Kudu client can allocate unbounded amounts of memory for error messages today, which is a potential problem for processes using the client. The API to get errors does have a way to indicate the errors overflowed the error buffer, but this isn't set yet.
> Given that error messages can vary significantly in size (as they include a var length string which will soon also include tracing output) and the row, the client should have a way to indicate the max buffer memory size rather than just some number of rows.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)