[
https://issues.apache.org/jira/browse/IMPALA-5785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henry Robinson resolved IMPALA-5785.
------------------------------------
Resolution: Fixed
Fix Version/s: (was: Impala 2.10.0)
Impala 2.0
This already happens for nodes that have ever run a query. See
https://github.com/apache/incubator-impala/blob/master/be/src/service/impala-server.cc#L1573.
My understanding is that is sufficient - if you've seen a bug that's
attributable to this not working, please attach some more information! We don't
have a lot of testing for this path.
> Purge local connection pool if node statestore marks node offline
> -----------------------------------------------------------------
>
> Key: IMPALA-5785
> URL: https://issues.apache.org/jira/browse/IMPALA-5785
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 2.9.0
> Reporter: Lars Volker
> Priority: Critical
> Fix For: Impala 2.0
>
>
> From time to time there seem to be issues with stale connection pool entries
> when nodes restart. In cases where the backend receives an update from the
> statestore that a node has gone offline, we should remove connections to that
> node from the connection pool.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
