You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Siddharth Wagle (JIRA)" <ji...@apache.org> on 2013/12/10 18:46:07 UTC
[jira] [Created] (AMBARI-4032) Ability to schedule a recurring
request execution of an Action/Command
Siddharth Wagle created AMBARI-4032:
---------------------------------------
Summary: 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.4#6159)