incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sumit Mohanty (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Deleted] (AMBARI-1426) Create cluster level Custom Action support
Date Tue, 16 Jul 2013 04:28:49 GMT

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

Sumit Mohanty updated AMBARI-1426:
----------------------------------

    Comment: was deleted

(was: Looks like INSTALL_FAILED is the state that causes this issue. Other combinations work
fine. The issue is that when a SCH is in INSTALL_FAILED state then only way to get out of
it is to perform a successful INSTALL.

* Tasks get created because, only SCH that are in MAINTENANCE or UNKNOWN are ignored
* SCH in INSTALL_FAILED do not go to UNKNOWN

Possible solutions:
* Do not create tasks when HOST is in HEARTBEAT_LOST or UNHEALTHY state
* Allow going into MAINTENANCE from more states than just INSTALLED

We should implement the first solution. The second one can be discussed for later.)
    
> Create cluster level Custom Action support
> ------------------------------------------
>
>                 Key: AMBARI-1426
>                 URL: https://issues.apache.org/jira/browse/AMBARI-1426
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 1.2.3
>            Reporter: Sumit Mohanty
>            Assignee: Sumit Mohanty
>             Fix For: 1.3.0
>
>
> * API changes for action definition
> * API changes to manage action results
> * DB changes for action definition and results
> ** Query support to get past results
> * Python template for actions
> * Server side support for creating an action
> ** POST handler for an action
> ** Validate the action parameters
> ** Create stage/task plan
> ** Return request/action id
> * Server side support for managing an action
> ** Monitor for action queue (enhance the request monitor)
> ** Evaluate host specific action results and update over-all action summary
> ** Handle timeouts
> * Agent support for executing an action
> ** Python script runner
> ** Provide default context
> ** Provide supplied inputs
> ** Reporting back the result and progress
> * Logging recommendations for custom actions
> * Modify setup to deploy custom-actions

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message