ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Nechiporenko (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMBARI-5159) Storm config page not available
Date Thu, 20 Mar 2014 13:12:43 GMT

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

Oleg Nechiporenko resolved AMBARI-5159.
---------------------------------------

    Resolution: Fixed

Committed to trunk.

> Storm config page not available
> -------------------------------
>
>                 Key: AMBARI-5159
>                 URL: https://issues.apache.org/jira/browse/AMBARI-5159
>             Project: Ambari
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.5.1
>            Reporter: Oleg Nechiporenko
>            Assignee: Oleg Nechiporenko
>             Fix For: 1.5.1
>
>         Attachments: AMBARI-5159.patch, ui.childopts-warning msg.png, ui.childopts.png
>
>
> Storm Config page not available.
> There is javascript-error.
> ui.childopts-property doesn't have a default value and Storm config-validator fails with
checking this property.
> The current behavior is that the {{ui.childopts}} is displayed without any defaultValue
(screenshot attached). The validator doesn't  invalidate this property which has no value.
Going ahead this property is silently deleted while applying configurations and does not appear
in the service config page post-installation.   
> The motive in the commit was to fetch the defaultValue from the stack instead of redeclaring
it on client side. 
> In this ticket we need to address following issues:
> # The default value for properties are being redeclared in {{getDefaults}} function of
storm_defaults_provider.js. We should fetch the defaultValue from the stack and should not
hard-code it in the client code. Actually the default value for ui.childopts got changed in
the stack definition with an earlier commit and it was not being reflected on service config
page as this was not changed in the client code.
> # Blank values should be marked as invalid. As of current behavior ui.childopts with
no value is not marked invalid. This is actually marked as invalid if user populate it once
and then clear it. 
> # Once we fetch the defaultValue from the stack for {{ui.childopts}} and change the property
value, the displayed warning message states the entire value as  {{Value is less than the
recommended default of -Xmx768m -Djava.security.auth.login.config=/etc/storm/storm_jaas.conf}}
(screenshot attached). The warning message should only include Xmx part and not other java
options.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message