[jira] [Commented] (AMBARI-7846) Change NameNode to start with: -XX:PermSize=128m -XX:MaxPermSize=256m by default

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-7846:
-----------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12675627/AMBARI-7846.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 38 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-client/groovy-client ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/249//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/249//console

This message is automatically generated.

> Change NameNode to start with: -XX:PermSize=128m -XX:MaxPermSize=256m by default
> --------------------------------------------------------------------------------
>
>                 Key: AMBARI-7846
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7846
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-client, ambari-server, ambari-web
>    Affects Versions: 1.7.0
>            Reporter: Srimanth Gunturi
>            Assignee: Srimanth Gunturi
>             Fix For: 1.7.0
>
>         Attachments: AMBARI-7846.patch
>
>
> PROBLEM: We have seen full GCs in multiple customer environments caused due to the current PermSize for the namenode being too low.
> GC entry that shows the issue:
> 2014-06-27T08:37:07.576+0000: 5030.881: [Full GC 5030.882: CMS: 29444717K->18807183K(80740352K), 135.6197500 secs 29685838K->18807183K(83571520K), 22577K->22479K(22784K)],+135.6199670+secs">*CMS Perm : 22577K->22479K(22784K)]* , 135.6199670 secs Times: user=134.95 sys=0.61, real=135.62 secs
> The settings which passes are:
> XX:PermSize=128m -XX:MaxPermSize=256m.



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