[jira] [Updated] (AMBARI-8224) Support action-level timeouts in Ambari

["Alejandro Fernandez (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMBARI-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alejandro Fernandez updated AMBARI-8224:
----------------------------------------
    Issue Type: Improvement  (was: Bug)

> Support action-level timeouts in Ambari
> ---------------------------------------
>
>                 Key: AMBARI-8224
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8224
>             Project: Ambari
>          Issue Type: Improvement
>    Affects Versions: 1.7.0
>            Reporter: Alejandro Fernandez
>
> In Ambari 1.7.0, there are several timeouts for running commands/actions
> First, ambari.properties has agent.task.timeout, which is a system-level timeout. If not specified, then Configuration.java sets AGENT_TASK_TIMEOUT_DEFAULT
> Further, in the stacks, each Component is free to define its own timeout, e.g.,
> {code}
> <component>
>   <name>NAMENODE</name>
>   <commandScript>
>   <script>scripts/namenode.py</script>
>     <scriptType>PYTHON</scriptType>
>     <timeout>600</timeout>
>   <commandScript>
> <component>
> {code}
> Normal actions (INSTALL, START, STOP) use the timeouts of the Component they are affecting. However, there is no way to set a specific timeout just for the INSTALL action, or the INSTALL action of any service.
> If a Component does not specify a timeout, it should inherit one from the Service.
> If the type of action also has a timeout, then the command of action T on Component Foo should use the maximum of the effective timeout of the Component, and the timeout specified for T (assuming that it exists).
> In Ambari 1.7.0, the code had to apply special logic just for the INSTALL action in order to get the yum commands to pass during the INSTALL action.
> See related Jira AMBARI-8220.



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