[
https://issues.apache.org/jira/browse/AMBARI-11804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-11804:
-----------------------------------
Attachment: AMBARI-11804.patch
> Improvements to agent level command retry
> -----------------------------------------
>
> Key: AMBARI-11804
> URL: https://issues.apache.org/jira/browse/AMBARI-11804
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
> Affects Versions: 2.1.0
> Reporter: Sumit Mohanty
> Assignee: Sumit Mohanty
> Fix For: 2.1.0
>
> Attachments: AMBARI-11804.patch
>
>
> Proposal:
> Introduce three config parameters in {{cluster-env}}
> * command_retry_enabled
> * command_retry_max_time_in_sec
> * commands_to_retry
> *command_retry_enabled* - true or false (default is false)
> *command_retry_max_time_in_sec* - how long to retry before giving up, default
> 0, which allows one try
> *commands_to_retry* - which commands are eligible for retry, if not set or
> empty then all commands are eligible, default "START"
> By default, retry for service check and custom commands (DECOMMISSION,
> RESTART, etc) are skipped
> As part of this change. properties from ambari.properties file will be
> removed. So only way to enable is to to provide configs in type cluster-env.
> So technically it can be disabled/enabled without restarting Ambari.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
