Hello Fawze, Impala considers a query 'FINISHED' when it is ready to return rows. The query only closes when the client closes it, or if it times out, the profile shows the query is still running (no end time, as you mentioned). In your version, the query will hold on to resources as long as the query is open (even if all rows have been fetched). This is tracked as IMPALA-1575, and gets much better in Impala 2.11.
HTH On Fri, 23 Nov 2018 at 23:29, Fawze Abujaber <fawz...@gmail.com> wrote: > Hi Community, > > I'm looking on issue with CM and Impala where i see in impala UI the query > still executing and in the query state it shown as FINISHED > > Looking at the query profile ( attached here), i see the query has no > finished time and from the other side i see the first rows fecthed and all > rows available. > > What i'm intersting in here to know if such query still hanging some > impala resources or not, and why my configuration didn't help here and the > query wasn't killed. > > BTW: > > I have the configuration of: > > Impala Command Line Argument Advanced Configuration Snippet (Safety Valve) > Impala (Service-Wide) > > idle_session_timeout=600 > idle_query_timeout=600 > > > > [image: image.png] > > Part of the query profile: > > Query Timeline > Query submitted: 119.16us (119160) > Planning finished: 482ms (482689616) > Ready to start on 7 backends: 561ms (561747089) > All 7 execution backends (8 fragment instances) started: 581ms > (581185065) > * Rows available: 34.73s (34732649614)* > * First row fetched: 36.81s (36806528086)* > -- > Take Care > Fawze Abujaber >
