Not YARN. I mean admission control actually. Resource pool is a term of
admission control.

On Thu, Jan 24, 2019 at 9:56 PM Boris Tyukin <bo...@boristyukin.com> wrote:

> good timing guys as we are looking for a good solution as well. Quanlong,
> when you say resource pool, do you mean YARN? HAve you looked into Impala
> admission control feature instead?
>
> On Thu, Jan 24, 2019 at 7:18 AM Quanlong Huang <huangquanl...@gmail.com>
> wrote:
>
>> It's quite a useful option!
>>
>> Looks like it cannot be set in per resource pool level. We have the use
>> case that queries from different resource pools need different timeout
>> limits. For example, some systems leverage Impala to build pre-aggregate
>> tables or other light-weight ETL jobs. EXEC_TIME_LIMIT_S of this pool may
>> be set as 30 minutes, while EXEC_TIME_LIMIT_S of adhoc query pool may be
>> set as 1 minutes.
>> Hopes this can be supported too. I just created IMPALA-8107 for this.
>>
>> Thanks,
>> Quanlong
>>
>> On Thu, Jan 24, 2019 at 2:59 PM Tim Armstrong <tarmstr...@cloudera.com>
>> wrote:
>>
>>> Yeah we got a lot of feedback asking for a solution to this :)
>>>
>>> On Wed, Jan 23, 2019 at 12:54 PM Fawze Abujaber <fawz...@gmail.com>
>>> wrote:
>>>
>>>> Amazing,
>>>>
>>>> Just on time because i'm planning to upgrade our clusters next week to
>>>> CDH 5.16.1 which includes impala 2.12
>>>>
>>>> On Wed, Jan 23, 2019 at 7:39 PM Tim Armstrong <tarmstr...@cloudera.com>
>>>> wrote:
>>>>
>>>>> EXEC_TIME_LIMIT_S is what you want:
>>>>> https://impala.apache.org/docs/build/html/topics/impala_exec_time_limit_s.html
>>>>>
>>>>>
>>>>> Those other configurations are based on idle time, but
>>>>> EXEC_TIME_LIMIT_S is based on the time spent executing.
>>>>>
>>>>> On Tue, Jan 22, 2019 at 6:36 PM Fawze Abujaber <fawz...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> How i can kill a query that running beyond specific time even if it
>>>>>> really doing calculations?
>>>>>>
>>>>>> I'm aware of the 3 timeout configuration that can be used by like
>>>>>> idle sessio timeout,idle,query timeout and query timeout S.
>>>>>>
>>>>>> My goal to kill anything that running/idle beyond 20 minutes because
>>>>>> for sure there is something to enhance in the query, i'm using the 3
>>>>>> parameters and i see queries running for few hours and i want some config
>>>>>> that can kill such queries.
>>>>>>
>>>>>> --
>>>>>> Take Care
>>>>>> Fawze Abujaber
>>>>>>
>>>>>
>>>>
>>>> --
>>>> Take Care
>>>> Fawze Abujaber
>>>>
>>>

Reply via email to