You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Lars Volker (JIRA)" <ji...@apache.org> on 2019/03/14 17:31:00 UTC
[jira] [Commented] (IMPALA-8310) Terminate impalad when HDFS call
thread pool is depleted
[ https://issues.apache.org/jira/browse/IMPALA-8310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16792895#comment-16792895 ]
Lars Volker commented on IMPALA-8310:
-------------------------------------
[~joemcdonnell], [~zoram] - I'm curious what you think about this one.
> 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-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org