[jira] [Commented] (AMBARI-16827) expose vm.overcommit_ratio on hawq-sysctl-env
[ https://issues.apache.org/jira/browse/AMBARI-16827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15304004#comment-15304004 ] Hadoop QA commented on AMBARI-16827: {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12806505/AMBARI-16827-2.patch against trunk revision . {color:red}-1 patch{color}. The patch command could not apply the patch. Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/7013//console This message is automatically generated. > expose vm.overcommit_ratio on hawq-sysctl-env > - > > Key: AMBARI-16827 > URL: https://issues.apache.org/jira/browse/AMBARI-16827 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary > Attachments: AMBARI-16827-2.patch, AMBARI-16827.patch > > > vm.overcommit_ratio is used for calculation of hawq_rm_memory_limit_perseg. > So, expose it on the UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16827) expose vm.overcommit_ratio on hawq-sysctl-env
[ https://issues.apache.org/jira/browse/AMBARI-16827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15303324#comment-15303324 ] Hudson commented on AMBARI-16827: - FAILURE: Integrated in Ambari-trunk-Commit #4936 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4936/]) AMBARI-16827: expose vm.overcommit_ratio on hawq-sysctl-env (bhuvnesh2703: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c2e0ef76ef858c2c182ead04774ab0e30e307120]) * ambari-server/src/main/resources/common-services/HAWQ/2.0.0/configuration/hawq-site.xml * ambari-server/src/main/resources/common-services/HAWQ/2.0.0/configuration/hawq-sysctl-env.xml * ambari-server/src/main/resources/common-services/HAWQ/2.0.0/themes/theme.json * ambari-server/src/test/python/stacks/2.3/HAWQ/test_service_advisor.py * ambari-server/src/main/resources/common-services/HAWQ/2.0.0/service_advisor.py > expose vm.overcommit_ratio on hawq-sysctl-env > - > > Key: AMBARI-16827 > URL: https://issues.apache.org/jira/browse/AMBARI-16827 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary > Attachments: AMBARI-16827-2.patch, AMBARI-16827.patch > > > vm.overcommit_ratio is used for calculation of hawq_rm_memory_limit_perseg. > So, expose it on the UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16827) expose vm.overcommit_ratio on hawq-sysctl-env
[ https://issues.apache.org/jira/browse/AMBARI-16827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15302522#comment-15302522 ] Hadoop QA commented on AMBARI-16827: {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12806030/AMBARI-16827.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 1 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in ambari-server. Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/6974//testReport/ Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/6974//console This message is automatically generated. > expose vm.overcommit_ratio on hawq-sysctl-env > - > > Key: AMBARI-16827 > URL: https://issues.apache.org/jira/browse/AMBARI-16827 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary > Attachments: AMBARI-16827.patch > > > vm.overcommit_ratio is used for calculation of hawq_rm_memory_limit_perseg. > So, expose it on the UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16827) expose vm.overcommit_ratio on hawq-sysctl-env
[ https://issues.apache.org/jira/browse/AMBARI-16827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299245#comment-15299245 ] Hadoop QA commented on AMBARI-16827: {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12806030/AMBARI-16827.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 1 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in ambari-server. Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/6949//testReport/ Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/6949//console This message is automatically generated. > expose vm.overcommit_ratio on hawq-sysctl-env > - > > Key: AMBARI-16827 > URL: https://issues.apache.org/jira/browse/AMBARI-16827 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary > Attachments: AMBARI-16827.patch > > > vm.overcommit_ratio is used for calculation of hawq_rm_memory_limit_perseg. > So, expose it on the UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)