[AMBARI-1205] Cannot persist service configuration when service is started

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.0
• Fix Version/s: 1.2.0, 1.2.1
• Component/s: ambari-server
• Assignee: Siddharth Wagle
• Reporter: Siddharth Wagle
• Created: 18/Jan/13 01:24
• Updated: 21/Jan/13 19:12
• Resolved: 21/Jan/13 19:12

Description

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.