[
https://issues.apache.org/jira/browse/IMPALA-10472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Quanlong Huang reassigned IMPALA-10472:
---------------------------------------
Assignee: Alexey Serbin
> Add a flag to control Kudu client connection negotiation timeout in backend
> ---------------------------------------------------------------------------
>
> Key: IMPALA-10472
> URL: https://issues.apache.org/jira/browse/IMPALA-10472
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Reporter: Alexey Serbin
> Assignee: Alexey Serbin
> Priority: Major
> Labels: Kudu, client, rpc
> Fix For: Impala 4.0.0
>
>
> Since [KUDU-2966|http://issues.apache.org/jira/browse/KUDU-2966] is
> addressed, it's now possible to control the RPC connection negotiation
> timeout from the Kudu client's side (C++ client). To use the newly
> introduced functionality in Impala's back-end, it's necessary to provide a
> control knob for that.
> This should help to address cases where busy/overloaded cluster nodes hosting
> Kudu tablet servers aren't fast enough to negotiate new connections within
> the default timeout interval (in most cases that's about Kudu server's
> connection negotiation threads being scheduled as needed and getting enough
> CPU time). In practice, it's necessary to customize the corresponding
> setting on the Kudu server side: it's controlled by the
> {{\-\-rpc_negotiation_timeout_ms}} flag for {{kudu-master}} and
> {{kudu-tserver}}.
> The idea is to add a gflag named like
> {{\-\-kudu_client_connection_negotiation_timeout_ms}} with default value of
> 3000. The default value 3000 is to keep the new code backwards-compatible.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
