[
https://issues.apache.org/jira/browse/AMBARI-13738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14992098#comment-14992098
]
Hadoop QA commented on AMBARI-13738:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12770796/AMBARI-13738.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 5 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:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server ambari-web:
org.apache.ambari.server.agent.AgentResourceTest
The test build failed in ambari-web
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/4181//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4181//console
This message is automatically generated.
> Checking the vm.swappiness Kernel Parameter
> -------------------------------------------
>
> Key: AMBARI-13738
> URL: https://issues.apache.org/jira/browse/AMBARI-13738
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-agent, ambari-server, ambari-web
> Reporter: Canan Girgin
> Priority: Trivial
> Attachments: AMBARI-13738.patch
>
>
> Swappiness parameter is set to 60 by default. This is not suitable for Hadoop
> clusters. When installing new cluster, Ambari should be check if the
> swappiness parameter is less than 10 .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
