[jira] [Commented] (IMPALA-7162) idle_query_timeout setting in Impala needs more clarification

2018-06-12 Thread Tim Armstrong (JIRA)


[ 
https://issues.apache.org/jira/browse/IMPALA-7162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16510091#comment-16510091
 ] 

Tim Armstrong commented on IMPALA-7162:
---

I just wanted to clarify that one particular point about resources, since 
cancelled queries now don't hold onto significant resources.

 

I think we could clarify the difference further of what being 
cancelled-but-open vs closed means since it's confusing - people wonder why the 
queries are still hanging around in some form (the reason is that they need to 
remain open for the client to be able to fetch status, profiles, etc).

> idle_query_timeout setting in Impala needs more clarification
> -
>
> Key: IMPALA-7162
> URL: https://issues.apache.org/jira/browse/IMPALA-7162
> Project: IMPALA
>  Issue Type: Documentation
>  Components: Docs
>Affects Versions: Impala 2.6.0
>Reporter: Laurel Hale
>Priority: Minor
>  Labels: documentation
>
> 1) Please refer to the following Impala documentation:
> [http://impala.apache.org/docs/build3x/html/topics/impala_timeouts.html]
> 2) Please see the section where idle_query_timeout is explained.
> *
> Request:-
> *
> We've mentioned that idle_query_timeout cancels the query.
> Can we please elaborate it further and mention that query still stays open 
> (after being cancelled) and consumes a slot in Impala admission control? 
> Therefore, though idle_query_timeout helps in saving some resources at Impala 
> end, you may still want to configure idle_Session_timeout to same value since 
> idle_Session_timeout even closes the query for idle sessions (instead of just 
> cancelling) though the requirement for it to trigger is session should stay 
> idle.



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

-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org



[jira] [Commented] (IMPALA-7162) idle_query_timeout setting in Impala needs more clarification

2018-06-12 Thread Laurel Hale (JIRA)


[ 
https://issues.apache.org/jira/browse/IMPALA-7162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16510081#comment-16510081
 ] 

Laurel Hale commented on IMPALA-7162:
-

[~tarmstrong] Is this not a valid issue?

> idle_query_timeout setting in Impala needs more clarification
> -
>
> Key: IMPALA-7162
> URL: https://issues.apache.org/jira/browse/IMPALA-7162
> Project: IMPALA
>  Issue Type: Documentation
>  Components: Docs
>Affects Versions: Impala 2.6.0
>Reporter: Laurel Hale
>Priority: Minor
>  Labels: documentation
>
> 1) Please refer to the following Impala documentation:
> [http://impala.apache.org/docs/build3x/html/topics/impala_timeouts.html]
> 2) Please see the section where idle_query_timeout is explained.
> *
> Request:-
> *
> We've mentioned that idle_query_timeout cancels the query.
> Can we please elaborate it further and mention that query still stays open 
> (after being cancelled) and consumes a slot in Impala admission control? 
> Therefore, though idle_query_timeout helps in saving some resources at Impala 
> end, you may still want to configure idle_Session_timeout to same value since 
> idle_Session_timeout even closes the query for idle sessions (instead of just 
> cancelling) though the requirement for it to trigger is session should stay 
> idle.



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

-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org



[jira] [Commented] (IMPALA-7162) idle_query_timeout setting in Impala needs more clarification

2018-06-12 Thread Tim Armstrong (JIRA)


[ 
https://issues.apache.org/jira/browse/IMPALA-7162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16510040#comment-16510040
 ] 

Tim Armstrong commented on IMPALA-7162:
---

After IMPALA-1575 cancelled queries don't consume slots in admission control 
(thankfully!).

> idle_query_timeout setting in Impala needs more clarification
> -
>
> Key: IMPALA-7162
> URL: https://issues.apache.org/jira/browse/IMPALA-7162
> Project: IMPALA
>  Issue Type: Documentation
>  Components: Docs
>Affects Versions: Impala 2.6.0
>Reporter: Laurel Hale
>Priority: Minor
>  Labels: documentation
>
> 1) Please refer to the following Impala documentation:
> [http://impala.apache.org/docs/build3x/html/topics/impala_timeouts.html]
> 2) Please see the section where idle_query_timeout is explained.
> *
> Request:-
> *
> We've mentioned that idle_query_timeout cancels the query.
> Can we please elaborate it further and mention that query still stays open 
> (after being cancelled) and consumes a slot in Impala admission control? 
> Therefore, though idle_query_timeout helps in saving some resources at Impala 
> end, you may still want to configure idle_Session_timeout to same value since 
> idle_Session_timeout even closes the query for idle sessions (instead of just 
> cancelling) though the requirement for it to trigger is session should stay 
> idle.



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

-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org