You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hawq.apache.org by "Ed Espino (JIRA)" <ji...@apache.org> on 2016/12/22 06:35:58 UTC
[jira] [Updated] (HAWQ-1162) Resource manager does not reference
dynamic minimum water level of each segment when it times out YARN
containers
[ https://issues.apache.org/jira/browse/HAWQ-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ed Espino updated HAWQ-1162:
----------------------------
Labels: (was: ToBeClosed)
> Resource manager does not reference dynamic minimum water level of each segment when it times out YARN containers
> -----------------------------------------------------------------------------------------------------------------
>
> Key: HAWQ-1162
> URL: https://issues.apache.org/jira/browse/HAWQ-1162
> Project: Apache HAWQ
> Issue Type: Bug
> Components: Resource Manager
> Reporter: Yi Jin
> Assignee: Amy
> Fix For: 2.1.0.0-incubating
>
>
> Then resource manager decides to timeout some containers from segments, the minimum water level number is passed as reference to avoid returning too many containers from some segments. There is a hard code 2.
> timeoutIdleGRMResourceToRBByRatio(i,
> retcontnum,
> &realretcontnum,
> mark->ClusterVCore > 0 ? 2 : 0 );
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)