[
https://issues.apache.org/jira/browse/IMPALA-7638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16634340#comment-16634340
]
Lars Volker commented on IMPALA-7638:
-------------------------------------
Thanks for the feedback, [~jfs]. Here's the relevant quote by [~sailesh] in the
review:
{quote}
We would also want the client connection timeout to default to a pretty high
number since on large clusters, we've seen Kerberos negotiations take up to a
few minutes.
I would prefer keeping the timeout to 5 minutes. It's not ideal, however, we
would rather not see queries fail because of timed out negotiations vs.
optimize for an even worse case of clients hung for 5 minutes (which is
configurable by a flag if the user chooses to do so). This is the same reason
we keep the internal connection timeout so high, since we'd rather see progress
than a failed query due to one timed out connection.
{quote}
I suspect that with KRPC enabled we should not see Kerberos negotiations take
several minutes, but we should confirm this with some stress tests.
> Lower default timeout for connection setup
> ------------------------------------------
>
> Key: IMPALA-7638
> URL: https://issues.apache.org/jira/browse/IMPALA-7638
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 3.1.0
> Reporter: Lars Volker
> Priority: Major
> Fix For: Impala 2.11.0
>
>
> IMPALA-5394 added the sasl_connect_tcp_timeout_ms flag with a default timeout
> of 5 minutes. This seems too long as broken clients will prevent new clients
> from establishing connections for this time. In addition to increasing the
> acceptor thread pool size (IMPALA-7565) we should lower this timeout
> considerably, e.g. to 5 seconds.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
