[
https://issues.apache.org/jira/browse/HAWQ-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979551#comment-14979551
]
ASF GitHub Bot commented on HAWQ-104:
-------------------------------------
GitHub user jiny2 opened a pull request:
https://github.com/apache/incubator-hawq/pull/54
HAWQ-104. HAWQ RM resource request timeout mechanism does not work
When yarn is not available or yarn has no enough resource to support query
running, the resource request of that query should be timed out based on
design. User should use guc to control the timeout value.
This fix is to make this work as before.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jiny2/incubator-hawq HAWQ-104
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-hawq/pull/54.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #54
----
commit 99433470855f6e2b7c8362c62bfecc1aecee9ade
Author: Yi Jin <y...@pivotal.io>
Date: 2015-10-29T00:26:59Z
HAWQ-104. HAWQ RM resource request timeout mechanism does not work
----
> HAWQ RM resource request timeout mechanism does not work
> --------------------------------------------------------
>
> Key: HAWQ-104
> URL: https://issues.apache.org/jira/browse/HAWQ-104
> Project: Apache HAWQ
> Issue Type: Bug
> Components: Resource Manager
> Reporter: Yi Jin
> Assignee: Yi Jin
>
> When yarn is not available or yarn has no enough resource to support query
> running, the resource request of that query should be timed out based on
> design. User should use guc to control the timeout value.
> This fix is to make this work as before.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
