[
https://issues.apache.org/jira/browse/HAWQ-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15063331#comment-15063331
]
ASF GitHub Bot commented on HAWQ-259:
-------------------------------------
GitHub user jiny2 opened a pull request:
https://github.com/apache/incubator-hawq/pull/197
HAWQ-259. YARN mode resource manager gets YARN cluster report once be…
The GRM cluster report is triggered only when there is at least one segment
registered through FTS heart-beat.
To handle the case, no segment is started in YARN mode, guc
hawq_rm_nocluster_timeout is introduced, if when resource manager has waited
for the possible segment registeration more than hawq_rm_nocluster_timeout
seconds, the resource requests are rejected due to no enough available segment.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jiny2/incubator-hawq HAWQ-259
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-hawq/pull/197.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 #197
----
----
> YARN mode resource manager gets YARN cluster report once before processing
> query resource request
> -------------------------------------------------------------------------------------------------
>
> Key: HAWQ-259
> URL: https://issues.apache.org/jira/browse/HAWQ-259
> Project: Apache HAWQ
> Issue Type: Improvement
> Components: Resource Manager
> Reporter: Yi Jin
> Assignee: Yi Jin
>
> If user submits request too fast after starting the whole cluster, the
> request is rejected because no available cluster yet.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
