[jira] [Commented] (AMBARI-15677) Ambari needs to set HDFS GC settings correctly
[ https://issues.apache.org/jira/browse/AMBARI-15677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16367167#comment-16367167 ] Hudson commented on AMBARI-15677: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8744 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8744/]) AMBARI-20747 - Upgrade is not taking care of AMBARI-15677 (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=665a2cd9b1747f87204f0406b029fd8186919c9a]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.4.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.4.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.4.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.3.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.4.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.6.xml > Ambari needs to set HDFS GC settings correctly > -- > > Key: AMBARI-15677 > URL: https://issues.apache.org/jira/browse/AMBARI-15677 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15677.patch > > > We need to make sure the Namenode CMS GC settings are correct. > Ambari does not currently set -XX:CMSInitiatingOccupancyFraction=70 or > -XX:+UseCMSInitiatingOccupancyOnly. The NewSize needs also some tweaking: it > should be 1/8th to 1/10th of the namenode heap size in general, but it looks > like we would cap at 8 gb like here (this NN has 112 GB heap). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-15677) Ambari needs to set HDFS GC settings correctly
[ https://issues.apache.org/jira/browse/AMBARI-15677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15978839#comment-15978839 ] Hudson commented on AMBARI-15677: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1430 (See [https://builds.apache.org/job/Ambari-branch-2.5/1430/]) AMBARI-20747 - Upgrade is not taking care of AMBARI-15677 (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=951bf19869eece2f798b4465e0b120f6db9a523f]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.4.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.3.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.4.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.4.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.4.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.5.xml > Ambari needs to set HDFS GC settings correctly > -- > > Key: AMBARI-15677 > URL: https://issues.apache.org/jira/browse/AMBARI-15677 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15677.patch > > > We need to make sure the Namenode CMS GC settings are correct. > Ambari does not currently set -XX:CMSInitiatingOccupancyFraction=70 or > -XX:+UseCMSInitiatingOccupancyOnly. The NewSize needs also some tweaking: it > should be 1/8th to 1/10th of the namenode heap size in general, but it looks > like we would cap at 8 gb like here (this NN has 112 GB heap). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-15677) Ambari needs to set HDFS GC settings correctly
[ https://issues.apache.org/jira/browse/AMBARI-15677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15978824#comment-15978824 ] Hudson commented on AMBARI-15677: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7335 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7335/]) AMBARI-20747 - Upgrade is not taking care of AMBARI-15677 (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=84d2b3a0ac3256d7d10c550d94814db3602f9ed7]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.4.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.4.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.4.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.4.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.3.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/config-upgrade.xml > Ambari needs to set HDFS GC settings correctly > -- > > Key: AMBARI-15677 > URL: https://issues.apache.org/jira/browse/AMBARI-15677 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15677.patch > > > We need to make sure the Namenode CMS GC settings are correct. > Ambari does not currently set -XX:CMSInitiatingOccupancyFraction=70 or > -XX:+UseCMSInitiatingOccupancyOnly. The NewSize needs also some tweaking: it > should be 1/8th to 1/10th of the namenode heap size in general, but it looks > like we would cap at 8 gb like here (this NN has 112 GB heap). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-15677) Ambari needs to set HDFS GC settings correctly
[
https://issues.apache.org/jira/browse/AMBARI-15677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223171#comment-15223171
]
Hadoop QA commented on AMBARI-15677:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12796676/AMBARI-15677.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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 test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6158//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6158//console
This message is automatically generated.
> Ambari needs to set HDFS GC settings correctly
> --
>
> Key: AMBARI-15677
> URL: https://issues.apache.org/jira/browse/AMBARI-15677
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15677.patch
>
>
> We need to make sure the Namenode CMS GC settings are correct.
> Ambari does not currently set -XX:CMSInitiatingOccupancyFraction=70 or
> -XX:+UseCMSInitiatingOccupancyOnly. The NewSize needs also some tweaking: it
> should be 1/8th to 1/10th of the namenode heap size in general, but it looks
> like we would cap at 8 gb like here (this NN has 112 GB heap).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
