[
https://issues.apache.org/jira/browse/IMPALA-9170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
YUBI LEE closed IMPALA-9170.
----------------------------
Resolution: Duplicate
> close idle connections without an associated session
> ----------------------------------------------------
>
> Key: IMPALA-9170
> URL: https://issues.apache.org/jira/browse/IMPALA-9170
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Affects Versions: Impala 3.3.0
> Reporter: Xiaomin Zhang
> Priority: Major
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> With the fix of IMPALA-7802, Impala now can close an idle connection after a
> configured interval. But it still leaves some connections opened which has no
> associated sessions:
> [https://github.com/cloudera/Impala/blob/cdh6.2.1/be/src/service/impala-server.cc#L2078]
> if (it == connection_to_sessions_map_.end()) return false;
> Some clients like HUE could use different connections to check the query
> status or fetch result. In these cases, those connections have no associated
> sessions, and not added into the connection_to_sessions_map. This caused
> issues when we use Radware to load balance Impala, because Radware does not
> send FIN to close an idle connection, but require backend to close idle
> connections.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
