[ 
https://issues.apache.org/jira/browse/AMBARI-14865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15141526#comment-15141526
 ] 

Hudson commented on AMBARI-14865:
---------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #4304 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4304/])
AMBARI-14865: Auto start - Maintenance mode of components should be 
(nsomasundaram: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ac5ca8fd1cd51360f7394c1fd85f8a062a4fb8e2])
* ambari-agent/src/test/python/ambari_agent/TestRecoveryManager.py
* ambari-agent/src/test/python/ambari_agent/TestActionQueue.py
* ambari-agent/src/main/python/ambari_agent/RecoveryManager.py
* ambari-server/src/main/java/org/apache/ambari/server/agent/RecoveryConfig.java
* 
ambari-server/src/main/java/org/apache/ambari/server/agent/HeartBeatHandler.java
* 
ambari-server/src/test/java/org/apache/ambari/server/agent/TestHeartbeatHandler.java


> Auto start: Maintenance mode of components should be respected when handling 
> agent registration.
> ------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-14865
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14865
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-agent, ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Nahappan Somasundaram
>            Assignee: Nahappan Somasundaram
>              Labels: ambari-agent, ambari-server
>             Fix For: 2.4.0
>
>         Attachments: rb43069 (1).patch, rb43069.patch
>
>
> Even if a service or component is set to auto start but is in maintenance 
> mode, it should not auto start. Components in maintenance mode (because 
> host/service is in maintenance mode) should not be enabled for auto start.
> Current implementation:
> In the current implementation we have both enabledComponents and 
> disabledComponents. To determine if a specified component is enabled for 
> recovery, an inclusive and exclusive test against enabledComponents and 
> disabledComponents is used. There is no support for excluding a component in 
> maintenance since that state is not available to the agent.
> To determine if a component marked for auto start is in maintenance state, 
> it's maintenance state has to be queried from the server, which makes it 
> cumbersome and agent managed. 
> New design:
> 1. Components to be enabled for auto start must be explicitly specified as 
> comma separated values in the enabledComponents section of the recovery 
> configuration. 
> 2. During agent registration, the server will determine if each of the 
> components marked for auto start is in maintenance mode or not and filter the 
> list before sending the list (enabledComponents) in the recovery 
> configuration to the agent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to