[
https://issues.apache.org/jira/browse/IMPALA-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16833216#comment-16833216
]
ASF subversion and git services commented on IMPALA-4874:
---------------------------------------------------------
Commit 23d7a6dce6ce4287edf20e3f63b225822cb88598 in impala's branch
refs/heads/master from Tim Armstrong
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=23d7a6d ]
IMPALA-8492: reenable large string tests in docker
IMPALA-4865 is fixed so these now pass. I noticed
that the IMPALA-4874 test occasionally hit
"Memory Limit Exceeded" when looped, so I reduced
the data size there slightly.
Testing:
Looped the tests locally against a dockerised minicluster
for a while.
Change-Id: I030f4eff2d3fb771fc92b760efb13170e68285dc
Reviewed-on: http://gerrit.cloudera.org:8080/13233
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Increase maximum KRPC message size
> ----------------------------------
>
> Key: IMPALA-4874
> URL: https://issues.apache.org/jira/browse/IMPALA-4874
> Project: IMPALA
> Issue Type: Sub-task
> Components: Distributed Exec
> Affects Versions: Impala 2.9.0
> Reporter: Henry Robinson
> Assignee: Joe McDonnell
> Priority: Major
> Fix For: Impala 2.12.0
>
>
> KRPC has a natural maximum message size (controlled by
> {{--rpc_max_message_size}}), but also uses Protobuf in such a way as the
> maximum message size is separately restricted to 512MB.
> Although Impala should try and avoid any payloads of this size, realistically
> we may not get rid of all of them by Impala 2.9.0. For now, let's increase
> the max message size while at the same time working to reduce the actual
> payload size created by Impala.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
