[jira] [Resolved] (IMPALA-5340) Query profile and debug webpage can disagree about 'Query State'

["Thomas Tauber-Marshall (JIRA)" <ji...@apache.org>]

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

Thomas Tauber-Marshall resolved IMPALA-5340.
--------------------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 2.9.0

commit ee9fbeca9041349d3532d315bf07e77d784a846d
Author: Thomas Tauber-Marshall <tm...@cloudera.com>
Date:   Thu May 18 12:50:48 2017 -0700

    IMPALA-5340: Query profile displays stale query state
    
    Previously, updates to the query state in ClientRequestState were
    not immediately reflected in the query profile, potentially
    leading to the profile showing an incorrect state for an extended
    perioud during execution.
    
    In particular, queries were being shown in the 'CREATED' state
    long after they had started 'RUNNING'.
    
    The fix is to update the profile whenever the state is updated.
    
    Testing:
    - Extended existing hs2 tests and added a beeswax test to check
      for expected query states in the profile
    
    Change-Id: I952319b7308a24d4e2dff924199c0c771bce25b3
    Reviewed-on: http://gerrit.cloudera.org:8080/6923
    Reviewed-by: Dan Hecht <dh...@cloudera.com>
    Reviewed-by: Thomas Tauber-Marshall <tm...@cloudera.com>
    Tested-by: Impala Public Jenkins

> Query profile and debug webpage can disagree about 'Query State'
> ----------------------------------------------------------------
>
>                 Key: IMPALA-5340
>                 URL: https://issues.apache.org/jira/browse/IMPALA-5340
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>            Reporter: Thomas Tauber-Marshall
>            Assignee: Thomas Tauber-Marshall
>            Priority: Critical
>              Labels: supportability
>             Fix For: Impala 2.9.0
>
>
> The problem is that even though both the query profile and the /queries debug web page set 'Query State' from the value ClientRequestState::query_state_, the debug web page always takes the current value, whereas the value in the profile is only updated at particular points during execution.
> This can lead to a situation where the profile's 'Query State' is stale and doesn't match the one in the debug web page, which is confusing.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)