[
https://issues.apache.org/jira/browse/AMBARI-9899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14345358#comment-14345358
]
Hadoop QA commented on AMBARI-9899:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12702190/AMBARI-9899_branch-2.0.0.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/1898//console
This message is automatically generated.
> Resource Manager Dashboard widget thresholds null after upgrade
> ---------------------------------------------------------------
>
> Key: AMBARI-9899
> URL: https://issues.apache.org/jira/browse/AMBARI-9899
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.0.0
> Reporter: Oleg Nechiporenko
> Assignee: Oleg Nechiporenko
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-9899.patch, AMBARI-9899_branch-2.0.0.patch
>
>
> I've noticed that after upgrading to Ambari 2.0 the Resource Manager Heap
> thresholds are set to 'null' instead of the previous values before the
> upgrade. This results in 4% utilization being 'red'.
> Systems Upgraded:
> * 1.5.1 to 2.0.0-458
> * 1.6.1 to 2.0.0-458
> * 1.7 to 2.0.0-458
> This state occurs in all upgrade situations. In this case I'm using MySQL as
> the Ambari DB See screenshots for additional details.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
