Hi Guys,
I'm still struggling with this, even i added QUERY_TIMEOUT_S=600 the query
still running, even it's select count(*) which produced already 1 row.
I'm wondering what configuration i can add to kill such queries.
Query (id=ef439d21f4fc51d3:4066675b00000000)
Summary
Session ID: ac46527a99fc7d27:c668cb8397badf84
Session Type: HIVESERVER2
HiveServer2 Protocol Version: V6
Start Time: 2018-12-04 02:58:23.479929000
End Time:
Query Type: QUERY
Query State: FINISHED
Query Status: OK
Impala Version: impalad version 2.10.0-cdh5.13.0 RELEASE (build
2511805f1eaa991df1460276c7e9f19d819cd4e4)
Delegated User:
Network Address: ::ffff:10.160.181.36:37485
Default Db: default
Sql Statement: select count(*) from xxxxxxxxxx where year=2018 and
month=10
Coordinator: xxxxxxxxxxx:22000
Query Options (set by configuration): SYNC_DDL=1,QUERY_TIMEOUT_S=600
Query Options (set by configuration and planner):
SYNC_DDL=1,QUERY_TIMEOUT_S=600,MT_DOP=0
On Mon, Nov 26, 2018 at 10:52 AM Fawze Abujaber <fawz...@gmail.com> wrote:
> Do you think i need to add the conf:
>
> QUERY_TIMEOUT_S
>
> On Mon, Nov 26, 2018 at 10:47 AM Fawze Abujaber <fawz...@gmail.com> wrote:
>
>> Hi jeszy,
>>
>> Thanks for your reply, i'm wondering if the configuration i have for the
>> query_timeout should kill this query.
>> and interesting to know why the query is hanging for so much time and i
>> want to know what was ongoing in this time.
>>
>> On Mon, Nov 26, 2018 at 10:45 AM Jeszy <jes...@gmail.com> wrote:
>>
>>> 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
>>>>
>>>
>>
>> --
>> Take Care
>> Fawze Abujaber
>>
>
>
> --
> Take Care
> Fawze Abujaber
>
--
Take Care
Fawze Abujaber
