[
https://issues.apache.org/jira/browse/KUDU-2966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17240951#comment-17240951
]
ASF subversion and git services commented on KUDU-2966:
-------------------------------------------------------
Commit 802057f3f243a6fa92c90b4da4c229307761762f in kudu's branch
refs/heads/master from Alexey Serbin
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=802057f ]
[CLI] introduce connection negotiation timeout
Since the connection negotiation timeout for Kudu client is now
configurable (see KUDU-2966 and changelist 62ec1e474), it makes sense
to allow using the new functionality in the kudu CLI tools.
This changelist introduces a new command line option/flag
--negotiation_timeout_ms to control the client-side connection
negotiation timeout in the kudu CLI tools. The default value for the
new flag is set to 3000 milliseconds to match the default connection
negotiation timeout on the server. With larger and heavy loaded
clusters it might be a good idea to the negotiation timeout if
connection negotiation timeouts happen time to time. Also, it could
help in cases where the RPC authentication is required and KDC is not
fast enough. Keep in mind that the total RPC timeout includes the
connection negotiation time, so in general it makes sense to bump
--timeout_ms along with --negotiation_timeout_ms by the same delta.
In addition, with this changeliest, all RPC-related kudu CLI tools
except for `kudu local_replica copy_from_remote` now have command line
arguments to control the RPC and the connection negotiation timeouts:
* timeout_ms
* negotiation_timeout_ms
In addition, this patch also unifies the way how KuduClient instances
are created in the kudu CLI code.
I'm planning to take care of the RPC-related parameters of the
`kudu local_replica copy_from_remote` tool in a separate patch.
Change-Id: I5627517fd1da4f4d7472f1f0af810d741efe3390
Reviewed-on: http://gerrit.cloudera.org:8080/16770
Tested-by: Alexey Serbin <aser...@cloudera.com>
Reviewed-by: Grant Henke <granthe...@apache.org>
> Make client negotiation timeouts configurable
> ---------------------------------------------
>
> Key: KUDU-2966
> URL: https://issues.apache.org/jira/browse/KUDU-2966
> Project: Kudu
> Issue Type: Bug
> Components: java, rpc
> Affects Versions: 1.11.0
> Reporter: Adar Dembo
> Priority: Major
>
> We saw a cluster in the wild where some negotiation steps between endpoints
> were additionally delayed for some small number of seconds. The existing
> {{\-\-rpc_negotiation_timeout_ms}} gflag can help workaround this on servers,
> but there's no equivalent in clients, whose negotiation timeouts are
> hardcoded to 3s in the C++ client and 10s in the Java client.
> It would be nice to expose a simple API to reconfigure the negotiation
> timeout.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
