[
https://issues.apache.org/jira/browse/AMBARI-10342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14394287#comment-14394287
]
Hadoop QA commented on AMBARI-10342:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12709206/AMBARI-10342.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:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/2234//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/2234//console
This message is automatically generated.
> Dependent config changes not being shown to user
> ------------------------------------------------
>
> Key: AMBARI-10342
> URL: https://issues.apache.org/jira/browse/AMBARI-10342
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 2.1.0
> Reporter: Andrii Babiichuk
> Assignee: Andrii Babiichuk
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-10342.patch
>
>
> According to the configs document, when the config
> yarn.scheduler.minimum-allocation-mb is updated, a bunch of other configs
> should be updated after call to /recommendations.
> From the UI when I make a change to yarn.scheduler.minimum-allocation-mb, I
> see the correct API call made. I also see one of the configs
> mapreduce.map.memory.mb's value change from 682 => 1024. However, there is no
> message saying 'X configs in Y services changed' etc.
> We should make sure that the response's values, min, max, step, etc. should
> be updated live in the configs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
