[jira] [Commented] (KUDU-2966) Make client negotiation timeouts configurable

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KUDU-2966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17225867#comment-17225867 ] 

ASF subversion and git services commented on KUDU-2966:
-------------------------------------------------------

Commit 62ec1e474167d79de298cd14d9e1b975bcdbdd8a in kudu's branch refs/heads/master from Alexey Serbin
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=62ec1e4 ]

[client] KUDU-2966 configure connection negotiation timeout

This patch addresses KUDU-2966 for the Kudu C++ client, making
the timeout for the connection negotiation configurable.  This patch
also contains a unit test for the newly introduced functionality.

As for the motivation for this patch: we have observed a few clusters
in the wild where connection negotiations were a bit slow when servers
are under heavy load.  It would be nice to control the connection
negotiation timeout at the client side as well, so at least kudu CLI
tool could use this functionality.

The newly introduced functionality is to be used at least in kudu CLI
(will be posted in a separate follow-up patch).

Change-Id: I8573a572887be041637e28e518a7cd3a6d1f1693
Reviewed-on: http://gerrit.cloudera.org:8080/16687
Tested-by: Alexey Serbin <as...@cloudera.com>
Reviewed-by: Andrew Wong <aw...@cloudera.com>


> 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)