[
https://issues.apache.org/jira/browse/IMPALA-8310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16792971#comment-16792971
]
Zoram Thanga commented on IMPALA-8310:
--------------------------------------
Sounds good to me.
That said, I wonder how the thread pool could be exhausted indefinitely. If the
timeout actually works, shouldn't the threads be available once again after
returning the timeout error status?
> 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: [email protected]
For additional commands, e-mail: [email protected]
