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 "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/03/05 04:33:00 UTC
[jira] [Commented] (IMPALA-8256)
ImpalaServicePool::RejectTooBusy() should print more meaningful message
[ https://issues.apache.org/jira/browse/IMPALA-8256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16784051#comment-16784051 ]
ASF subversion and git services commented on IMPALA-8256:
---------------------------------------------------------
Commit 63d45d59bae3fb37571088c0a2418a9df7630c51 in impala's branch refs/heads/master from Michael Ho
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=63d45d5 ]
IMPALA-8256: Better error message for ImpalaServicePool::RejectTooBusy()
An incoming request to a RPC service can be rejected due to either
exceeding the memory limit or maximum allowed queue length.
It's unclear from the current error message which of those factors
contributes to the failure as neither the actual queue length nor
the memory consumption is printed.
This patch fixes the problem by printing the estimated queue length
and memory consumption when a RPC request is dropped.
Testing done: verified the new error message with test_rpc_timeout.py
Change-Id: If0297658acf2b23823dcb7d2bdff5d8e4475bb98
Reviewed-on: http://gerrit.cloudera.org:8080/12624
Reviewed-by: Impala Public Jenkins <im...@cloudera.com>
Tested-by: Impala Public Jenkins <im...@cloudera.com>
> ImpalaServicePool::RejectTooBusy() should print more meaningful message
> ------------------------------------------------------------------------
>
> Key: IMPALA-8256
> URL: https://issues.apache.org/jira/browse/IMPALA-8256
> Project: IMPALA
> Issue Type: Bug
> Components: Distributed Exec
> Affects Versions: Impala 2.12.0, Impala 3.1.0, Impala 3.2.0
> Reporter: Michael Ho
> Assignee: Michael Ho
> Priority: Major
>
> An RPC request to a service can be rejected either due to exceeding the memory limit or maximum allowed queue length. It's unclear from the current error message which of those factors contribute to the failure as neither the actual queue length nor the memory consumption is printed.
--
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