ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-16646) Set vm.overcommit_memory dynamically for HAWQ
Date Sat, 14 May 2016 01:45:13 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-16646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15283367#comment-15283367
] 

Hudson commented on AMBARI-16646:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #4841 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4841/])
AMBARI-16646: Set vm.overcommit_memory dynamically for HAWQ (mithmatt) (matt: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4cb895c6cda9a3abd03ff163eebc61f1c61d4eaf])
* ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py
* ambari-server/src/main/resources/common-services/HAWQ/2.0.0/service_advisor.py
* ambari-server/src/main/resources/stacks/service_advisor.py
* ambari-server/src/test/python/stacks/2.3/HAWQ/test_service_advisor.py


> Set vm.overcommit_memory dynamically for HAWQ
> ---------------------------------------------
>
>                 Key: AMBARI-16646
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16646
>             Project: Ambari
>          Issue Type: Bug
>          Components: stacks
>            Reporter: Matt
>            Assignee: Matt
>            Priority: Minor
>             Fix For: trunk, 2.4.0
>
>         Attachments: AMBARI-16646-trunk-orig.patch, AMBARI-16646-trunk-v1.patch
>
>
> Consider all HAWQ host machines. 
> If the lowest memory among all systems is >= 32 GB set vm.overcommit_memory as 2,
else use 1



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message