[
https://issues.apache.org/jira/browse/AMBARI-12059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14595279#comment-14595279
]
Hudson commented on AMBARI-12059:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #2965 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2965/])
AMBARI-12059. YARN tab should be before MapReduce2 tab when setting up configs
in the launch wizard (alexantonenko) (hiveww:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=03bb08558445739fc89d34932df13b34f3aa01a2)
* ambari-web/app/models/stack_service.js
* ambari-web/test/views/main/host/summary_test.js
> YARN tab should be before MapReduce2 tab when setting up configs in the
> launch wizard
> -------------------------------------------------------------------------------------
>
> Key: AMBARI-12059
> URL: https://issues.apache.org/jira/browse/AMBARI-12059
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.0
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Fix For: 2.2.0
>
> Attachments: AMBARI-12059.patch
>
>
> MR configs rely on YARN configs for certain sizing i.e. map memory and reduce
> memory is dependent on yarn minimum allocation.
> When trying to size MR configs, the minimum limit starts 0.66 GB on a 2 node
> vagrant cluster. There is no clear indication to the user why this min limit
> is setup. Allow the user to progress to YARN first before tweaking MR
> configs would be better.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
