[
https://issues.apache.org/jira/browse/KUDU-3595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashwani Raina resolved KUDU-3595.
---------------------------------
Fix Version/s: 1.18
Resolution: Fixed
> Add a way to set Kudu client's rpc_max_message_size via KuduClientBuilder
> -------------------------------------------------------------------------
>
> Key: KUDU-3595
> URL: https://issues.apache.org/jira/browse/KUDU-3595
> Project: Kudu
> Issue Type: Task
> Components: client
> Affects Versions: 1.17.0
> Reporter: Joe McDonnell
> Assignee: Ashwani Raina
> Priority: Major
> Fix For: 1.18
>
>
> In some Impala workloads, we have seen issues fetching data from Kudu,
> because the RPC message size exceeds the rpc_max_message_size for the Kudu
> client (which defaults to 50MB). This is likely due to very large strings or
> binary data. See IMPALA-13202.
> We should add a way to tune the rpc_max_message_size for the Kudu client. In
> discussions on IMPALA-13202, the option we preferred is to add a way to
> specify this on the KuduClientBuilder (similar to how we handle num_reactors
> today).
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
