[
https://issues.apache.org/jira/browse/KUDU-3595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17894745#comment-17894745
]
ASF subversion and git services commented on KUDU-3595:
-------------------------------------------------------
Commit 351ae9bfdbb7eb10165454e64f21c189ea776cbc in kudu's branch
refs/heads/branch-1.18.x from Ashwani Raina
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=351ae9bfd ]
KUDU-3595: Add interface to set rpc_max_message_size for C++ client
Kudu client's default capacity to hold RPC payload prove to be less
in cases where payload size goes beyond 50MB (default max size).
This patch adds a method to KuduClientBuilder that enables clients
to change the default max size for RPC message per application needs.
For server, value remains set to default i.e. rpc_max_message_size.
If the default value for server is changed by setting the flag, the
same value gets applied to the subsequent inbound transfer object.
Unit test (TestRpcSidecarWithSizeLimits) tests two scenarios:
1. RPC max message size at client is greater or equal to the size
of message being received from server - Completes successfully.
2. RPC max message size at client is less than the size of message
being received from server - Op fails with shutting down of client
connection and appropriate error message.
Change-Id: Ib8feb5ba92ea604442a643e3286944564e655fa6
Reviewed-on: http://gerrit.cloudera.org:8080/21622
Reviewed-by: Alexey Serbin <ale...@apache.org>
Tested-by: Alexey Serbin <ale...@apache.org>
(cherry picked from commit 66794ac0970a6313e7a081720424228fdf8a5617)
Reviewed-on: http://gerrit.cloudera.org:8080/22002
Reviewed-by: Abhishek Chennaka <achenn...@cloudera.com>
> 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)
