ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Wagle (JIRA)" <>
Subject [jira] [Updated] (AMBARI-1205) Cannot persist service configuration when service is started
Date Fri, 18 Jan 2013 01:27:11 GMT


Siddharth Wagle updated AMBARI-1205:

    Attachment: patch_3345.txt

Patch for not throwing exception + unit test
> Cannot persist service configuration when service is started
> ------------------------------------------------------------
>                 Key: AMBARI-1205
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: controller
>    Affects Versions: 1.2.0
>            Reporter: Siddharth Wagle
>            Assignee: Siddharth Wagle
>         Attachments: patch_3345.txt
> 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 BUG-3182 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:

View raw message