ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Wagle (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMBARI-4032) Ability to schedule a recurring request execution of an Action/Command
Date Fri, 24 Jan 2014 00:27:37 GMT

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

Siddharth Wagle resolved AMBARI-4032.
-------------------------------------

    Resolution: Fixed

All sub-tasks closed.

> Ability to schedule a recurring request execution of an Action/Command
> ----------------------------------------------------------------------
>
>                 Key: AMBARI-4032
>                 URL: https://issues.apache.org/jira/browse/AMBARI-4032
>             Project: Ambari
>          Issue Type: New Feature
>          Components: controller
>    Affects Versions: 1.5.0
>            Reporter: Siddharth Wagle
>            Assignee: Siddharth Wagle
>             Fix For: 1.5.0
>
>
> *Definitions*
> _Request Schedule Resource_
> A request schedule resource captures all the information required to create a request
for executing a “Custom Action” or a “Custom Command” or a “First Class Command:
(Start, Stop, Restart)” with a recurring schedule or a point in time execution if no schedule
is specified.
> *Scenarios to support*
> 1. _Rolling restart of Host Components / Service components_
> Restart services with zero/minimal downtime for upgrades or configuration changes. You
can do a rolling restart on individual services (HDFS, MapReduce, HBase, ZooKeeper, etc).
Rolling restart also lets you choose which service components (Namenode, etc.) to restart.
> 2. _Rebalancer_
> Rebalancer is a sample of a custom action that can be executed to initiate HDFS block
rebalance. This could be a one time task or a recurring task (e.g. rebalance once each week
at a specific time).



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message