You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Oleg Nechiporenko (JIRA)" <ji...@apache.org> on 2013/11/26 12:53:35 UTC

[jira] [Updated] (AMBARI-3884) Validate string-type dynamic configs in YARN and MR2

     [ https://issues.apache.org/jira/browse/AMBARI-3884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oleg Nechiporenko updated AMBARI-3884:
--------------------------------------

    Attachment: AMBARI-3884.patch

> Validate string-type dynamic configs in YARN and MR2
> ----------------------------------------------------
>
>                 Key: AMBARI-3884
>                 URL: https://issues.apache.org/jira/browse/AMBARI-3884
>             Project: Ambari
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.4.1
>            Reporter: Oleg Nechiporenko
>            Assignee: Oleg Nechiporenko
>             Fix For: 1.5.0
>
>         Attachments: AMBARI-3884.patch
>
>
> We have configs where portions of it are dynamically calculated:
> * mapreduce.map.java.opts
> * mapreduce.reduce.java.opts
> * yarn.app.mapreduce.am.command-opts
> For example we calculate "1024" in the ultimate value of "-Xmx1024m". When the user messes it up (say "-Xmx100m"), we do not validate correctly. The validators for the above properties need to be smarter to show warnings.
> The validators have to be robust so that they can tolerate very complex strings and error cases.



--
This message was sent by Atlassian JIRA
(v6.1#6144)