[
https://issues.apache.org/jira/browse/KUDU-2966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Serbin resolved KUDU-2966.
---------------------------------
Fix Version/s: 1.14.0
Resolution: Fixed
This is addressed for C++ client and kudu CLI tools correspondingly.
For the Java side, I opened a separate JIRA:
https://issues.apache.org/jira/browse/KUDU-3240
> Make client negotiation timeouts configurable
> ---------------------------------------------
>
> Key: KUDU-2966
> URL: https://issues.apache.org/jira/browse/KUDU-2966
> Project: Kudu
> Issue Type: Bug
> Components: api, client, rpc
> Affects Versions: 1.11.0
> Reporter: Adar Dembo
> Priority: Major
> Fix For: 1.14.0
>
>
> 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)
