[
https://issues.apache.org/jira/browse/IMPALA-7800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga resolved IMPALA-7800.
----------------------------------
Resolution: Fixed
Fix Version/s: Impala 3.3.0
> Reject or timeout new incoming connections once --fe_service_threads limit is
> reached
> -------------------------------------------------------------------------------------
>
> Key: IMPALA-7800
> URL: https://issues.apache.org/jira/browse/IMPALA-7800
> Project: IMPALA
> Issue Type: Improvement
> Components: Clients
> Affects Versions: Impala 3.0, Impala 2.12.0
> Reporter: Michael Ho
> Assignee: Zoram Thanga
> Priority: Major
> Fix For: Impala 3.3.0
>
>
> Currently, the number of frontend service threads is controlled by
> {{--fe_service_threads}}. Once this limit is reached, the worker threads of
> {{connection_setup_pool}} will block until some of the service threads exit.
> New incoming connections will be buffered in a queue in
> {{connection_setup_pool}} until it fills up. Currently, there is no time out
> for all these buffered connections in the queue. Consequently, if the number
> of frontend service threads max'ed out for an extended period of time, a
> client trying to connect to Impala will feel "stuck" until a front end
> service thread is available.
> We should consider either rejecting any new connections once
> {{--fe_service_threads}} limit is reached or imposing a tunable upper bound
> on the wait time for connections in the queue to improve the users'
> experience. cc'ing [~zoram]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
