[AMBARI-4032] Ability to schedule a recurring request execution of an Action/Command

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5.0
• Fix Version/s: 1.5.0
• Component/s: ambari-server
• Assignee: Siddharth Wagle
• Reporter: Siddharth Wagle
• Created: 10/Dec/13 17:44
• Updated: 24/Jan/14 00:25
• Resolved: 24/Jan/14 00:25

Description

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).

Issue Links

• is related to: AMBARI-4256 Time interval between batches in a request_schedule should be in seconds
• requires: AMBARI-4267 Enable BatchRequest(s) to transform to API calls to the server
• requires: AMBARI-4306 Request Schedule status not updated for Point in time execution request
• requires: AMBARI-4027 Define RequestSchedule DAO and relational schema
• requires: AMBARI-4033 Define the RequestSchedule API endpoint
• requires: AMBARI-4034 Create the RequestSchedule resource provider
• requires: AMBARI-4150 Provide ability to batch requests based on schedule
• requires: AMBARI-4293 Support tolerance level for batched requests based on task status