incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Wagle (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-1205) Cannot persist service configuration when service is started
Date Fri, 18 Jan 2013 02:32:13 GMT

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

Siddharth Wagle updated AMBARI-1205:
------------------------------------

    Attachment:     (was: patch_3345.txt)
    
> Cannot persist service configuration when service is started
> ------------------------------------------------------------
>
>                 Key: AMBARI-1205
>                 URL: https://issues.apache.org/jira/browse/AMBARI-1205
>             Project: Ambari
>          Issue Type: Bug
>          Components: controller
>    Affects Versions: 1.2.0
>            Reporter: Siddharth Wagle
>            Assignee: Siddharth Wagle
>         Attachments: AMBARI-1205.patch
>
>
> There is a backend requirement that for the service config to be saved (on service level
or host_component level), the service has to be stopped. 
> This is problematic when implementing because a save of 'global' config effects all host_components.
If I change an OOZIE property in 'global', I have to persist that change in NAMENODE, DATANODE,
etc. But these services are still running and hence cannot be persisted.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message