You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Nahappan Somasundaram (JIRA)" <ji...@apache.org> on 2016/05/18 21:43:12 UTC
[jira] [Updated] (AMBARI-16749) Auto-start services: Ambari agent
should set auto_start_only to True when recovery_type is AUTO_START
[ https://issues.apache.org/jira/browse/AMBARI-16749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nahappan Somasundaram updated AMBARI-16749:
-------------------------------------------
Summary: Auto-start services: Ambari agent should set auto_start_only to True when recovery_type is AUTO_START (was: Auto-start services: Ambari agent should set auto_start_only to True explicitly if recovery_type is AUTO_START)
> Auto-start services: Ambari agent should set auto_start_only to True when recovery_type is AUTO_START
> -----------------------------------------------------------------------------------------------------
>
> Key: AMBARI-16749
> URL: https://issues.apache.org/jira/browse/AMBARI-16749
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
> Affects Versions: 2.4.0
> Reporter: Nahappan Somasundaram
> Assignee: Nahappan Somasundaram
> Fix For: 2.4.0
>
>
> In ambari agent recoveryManager.py, if recovery type is AUTO_START, recovery_enabled and auto_start_only should be set to True explicitly. However, only recovery_enabled is set to True while auto_start_only is initially set to True and then flipped to False if the recovery type is FULL. When recovery is not enabled, auto_start_only is True which is not correct though auto_start_only is not used if recovery_enabled is False. But this is just a side effect and is a potential bug.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)