[jira] [Updated] (IMPALA-5043) Flag when Impala daemon is disconnected from statestore
[ https://issues.apache.org/jira/browse/IMPALA-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-5043: -- Issue Type: Bug (was: Improvement) > Flag when Impala daemon is disconnected from statestore > --- > > Key: IMPALA-5043 > URL: https://issues.apache.org/jira/browse/IMPALA-5043 > Project: IMPALA > Issue Type: Bug > 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 6ms. 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-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-5043) Flag when Impala daemon is disconnected from statestore
[ https://issues.apache.org/jira/browse/IMPALA-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-5043: -- Target Version: Impala 3.2.0 Summary: Flag when Impala daemon is disconnected from statestore (was: When daemons are disconnected from the Statestore they can show incorrect admission control limits) > Flag when Impala daemon is 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 >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 6ms. 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-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org