[
https://issues.apache.org/jira/browse/AMBARI-12813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14905371#comment-14905371
]
Hadoop QA commented on AMBARI-12813:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12761925/AMBARI-12813.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 4 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/3842//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3842//console
This message is automatically generated.
> Increase OS kernel parameters for hbase
> ---------------------------------------
>
> Key: AMBARI-12813
> URL: https://issues.apache.org/jira/browse/AMBARI-12813
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Juanjo Marron
> Assignee: Juanjo Marron
> Fix For: 2.1.2
>
> Attachments: AMBARI-12813.patch
>
>
> Ambari recipes generate /etc/security/limits.d/[service].conf to limit the
> open file, and number of processes for each user. It appears that hbase
> service is not doing this while hdfs, hive , ams, yarn, maprdeduce ... are
> cretaing their own user limits
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
