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/02/10 20:25:01 UTC
[jira] [Commented] (IMPALA-5043) Admission control error messages
don't hint that information is stale when disconnected from statestore
[ https://issues.apache.org/jira/browse/IMPALA-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16764549#comment-16764549 ]
ASF subversion and git services commented on IMPALA-5043:
---------------------------------------------------------
Commit c3c69ae362ae06adcf304b8610221a656e7b2eba in impala's branch refs/heads/master from Tim Armstrong
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=c3c69ae ]
IMPALA-5043: diagnostics for topic staleness in AC
The default threshold for the admission control topic to be considered
stale is 5s.
Adds diagnostics for stale topic updates:
* A banner on the /admission web UI if the topic is considered stale.
* Time since last update on the /admission web UI
* Append a warning to rejection/queuing messages where topic staleness
may have affected the decision.
* Append a warning to profiles of admitted queries where the topic was
stale at the time the query was admitted.
* Include the topic staleness in all profiles of admitted queries
Testing:
Add a custom cluster test that kills the statestore, validates that
admission control behaves as expected and that stateless warnings
show up in the appropriate places.
Change-Id: Ib9e26adb6419589ccf7625e423356df45bee4ac9
Reviewed-on: http://gerrit.cloudera.org:8080/12407
Reviewed-by: Impala Public Jenkins <im...@cloudera.com>
Tested-by: Impala Public Jenkins <im...@cloudera.com>
> Admission control error messages don't hint that information is stale when disconnected from statestore
> -------------------------------------------------------------------------------------------------------
>
> Key: IMPALA-5043
> URL: https://issues.apache.org/jira/browse/IMPALA-5043
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Affects Versions: Impala 2.6.0
> Reporter: Thomas Scott
> Assignee: Tim Armstrong
> Priority: Major
> Labels: admission-control, resource-management, supportability
>
> When (for whatever reason) one or more daemons are disconnected from the statestore the admission control data held on the daemon goes stale. This can lead to the daemon accepting queries when there is not capacity or rejecting queries when there is capacity.
> For example, a pool somepool has a limit of 10 concurrent queries and is at that limit when a daemon is disconnected from the statestore. Even when other queries in somepool finish and the pool is now empty the disconnected daemon will report the following when new queries are executed:
> ERROR: Admission for query exceeded timeout 60000ms. Queued reason: number of running queries 10 is over limit 10
> Could we have some warning to say that the admission control data is stale here?
--
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