[jira] [Updated] (IMPALA-9636) Retried queries that blacklist nodes should ensure they don't run on the blacklisted node

["Quanlong Huang (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IMPALA-9636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Quanlong Huang updated IMPALA-9636:
-----------------------------------
    Priority: Critical  (was: Major)

> Retried queries that blacklist nodes should ensure they don't run on the blacklisted node
> -----------------------------------------------------------------------------------------
>
>                 Key: IMPALA-9636
>                 URL: https://issues.apache.org/jira/browse/IMPALA-9636
>             Project: IMPALA
>          Issue Type: Sub-task
>            Reporter: Sahil Takiar
>            Priority: Critical
>
> When a query is retried due to a node blacklisting event, there is no guarantee that the retried query will *not* run on the blacklisted node. When a node is blacklisted, it is only placed on the blacklist for a certain period of time (the first time it is blacklisted I think it is only about 12 seconds). It is possible that retrying the query takes a while (perhaps the query has to wait in the admission control queue again). So it is possible that the retried query will end up running on the node that it blacklisted during its original attempt, which is probably unwise because that node caused the query to fail.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org