You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Srimanth Gunturi (JIRA)" <ji...@apache.org> on 2014/10/18 02:09:34 UTC

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

Srimanth Gunturi created AMBARI-7846:
----------------------------------------

             Summary: 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


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)