[
https://issues.apache.org/jira/browse/IMPALA-8310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16793982#comment-16793982
]
Joe McDonnell commented on IMPALA-8310:
---------------------------------------
I think this would be the right thing to do. We should dump appropriate state
when it happens. Another option is to report this node as incapable of
executing queries to the statestore, but I think I prefer aborting the impalad.
[~zoram] The caller thread messages a thread pool, which does the actual IO.
When the caller times out, the thread doing the actual IO call is still stuck.
The thread pool has a fixed capacity and can run out.
> Terminate impalad when HDFS call thread pool is depleted
> --------------------------------------------------------
>
> Key: IMPALA-8310
> URL: https://issues.apache.org/jira/browse/IMPALA-8310
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 3.2.0
> Reporter: Lars Volker
> Priority: Major
>
> JVM hangs will currently consume the thread pool added in IMPALA-7738. Once
> the pool is depleted we abort new queries. Instead we should consider killing
> the Impalad since it is in a state where it won’t be able to process queries
> until it is restarted.
--
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
