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/09/18 23:47:34 UTC

[jira] [Commented] (AMBARI-7394) Recommend properties were changed after cluster install

    [ https://issues.apache.org/jira/browse/AMBARI-7394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139578#comment-14139578 ] 

Srimanth Gunturi commented on AMBARI-7394:
------------------------------------------

The reason this is happening is that when installing, all services are provided and memory distributed accordingly. After install when editing configs, we only provide the service we are editing, and this one service is distributed across all hosts, causing issues.
Also, another reason is that any machines with memory over 15GB cause another code path - cause this issue to not reproduce in certain environments.

> Recommend properties were changed after cluster install
> -------------------------------------------------------
>
>                 Key: AMBARI-7394
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7394
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 1.7.0
>            Reporter: Srimanth Gunturi
>            Assignee: Srimanth Gunturi
>            Priority: Critical
>             Fix For: 1.7.0
>
>         Attachments: recommendAfterInstall.png
>
>
> Was installed single-node cluster with all services and default configuration.
> During install was checked that recommend values for "Map-side sort buffer memory", "yarn.app.mapreduce.am.resource.mb", "yarn.app.mapreduce.am.command-opts" were used for install ("410", "1024" and "-Xmx819m").
> After install was try to add new property to MapReduce2 service - after "Save" button click was opened "Configurations" window with greater recommended values than before install.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)