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

Tim Armstrong resolved IMPALA-2626.
-----------------------------------
    Resolution: Duplicate

> In-flight queries fail when statestore comes back online.
> ---------------------------------------------------------
>
>                 Key: IMPALA-2626
>                 URL: https://issues.apache.org/jira/browse/IMPALA-2626
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Distributed Exec
>    Affects Versions: Impala 2.3.0
>            Reporter: Sailesh Mukil
>            Assignee: Sailesh Mukil
>            Priority: Minor
>              Labels: chaosmonkey, statestore, usability
>
> During a session, if the statestore goes down, the impalads continue 
> execution if they have enough metadata that they've already received from the 
> statestore prior to it's failure.
> The impalads can continue execution without the statestore with the stale 
> metadata that they posses. However, when the statestore comes back online, 
> the first membership callback it makes to the impalad hosts, erases the 
> "known_backends" list that the impalads have stored locally.
> Therefore, in-flight queries fail(sometimes without propagating the error to 
> the shell -> IMPALA-1325).
> Solution:
> Do not erase the list of "known_backends" in each impalad until the 
> statestore has a new list to provide to the impalads.
> _This bug was found during initial runs of ChaosMonkey on Impala._



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to