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

Posted to issues@calcite.apache.org by "Karan Mehta (JIRA)" <ji...@apache.org> on 2018/08/29 17:41:00 UTC

[jira] [Created] (CALCITE-2503) AvaticaCommonsHttpClientImpl client needs to set user-token on HttpClientContext before sending the request

Karan Mehta created CALCITE-2503:
------------------------------------

             Summary: AvaticaCommonsHttpClientImpl client needs to set user-token on HttpClientContext before sending the request
                 Key: CALCITE-2503
                 URL: https://issues.apache.org/jira/browse/CALCITE-2503
             Project: Calcite
          Issue Type: Improvement
            Reporter: Karan Mehta
            Assignee: Karan Mehta


One of the Avatica client implementations, AvaticaCommonsHttpClientImpl, uses a PoolingHttpClientConnectionManager. When using mutual authentication on the client pool, we need to ensure that we are setting a user-token on the HttpClientContext, otherwise it ends up creating a new connection everytime and not reusing it. See:  [https://hc.apache.org/httpcomponents-client-ga/tutorial/html/advanced.html] for more details

This results in significant perf degradation since every new connection tries to complete a SSL handshake (which is expensive)

See: https://stackoverflow.com/questions/548029/how-much-overhead-does-ssl-impose



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)