You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Alexey Serbin (Jira)" <ji...@apache.org> on 2021/02/02 23:19:00 UTC

[jira] [Assigned] (KUDU-2966) Make connection negotiation timeouts configurable for C++ client

     [ https://issues.apache.org/jira/browse/KUDU-2966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Serbin reassigned KUDU-2966:
-----------------------------------

      Assignee: Alexey Serbin
    Issue Type: Improvement  (was: Bug)

> Make connection negotiation timeouts configurable for C++ client
> ----------------------------------------------------------------
>
>                 Key: KUDU-2966
>                 URL: https://issues.apache.org/jira/browse/KUDU-2966
>             Project: Kudu
>          Issue Type: Improvement
>          Components: api, client, rpc
>    Affects Versions: 1.11.0
>            Reporter: Adar Dembo
>            Assignee: Alexey Serbin
>            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)