Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 26BF31040F for ; Fri, 24 Jan 2014 00:27:39 +0000 (UTC) Received: (qmail 83298 invoked by uid 500); 24 Jan 2014 00:27:38 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 83243 invoked by uid 500); 24 Jan 2014 00:27:37 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 83233 invoked by uid 99); 24 Jan 2014 00:27:37 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Jan 2014 00:27:37 +0000 Date: Fri, 24 Jan 2014 00:27:37 +0000 (UTC) From: "Siddharth Wagle (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (AMBARI-4032) Ability to schedule a recurring request execution of an Action/Command MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-4032?page=3Dcom.atlassi= an.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 crea= te a request for executing a =E2=80=9CCustom Action=E2=80=9D or a =E2=80=9C= Custom Command=E2=80=9D or a =E2=80=9CFirst Class Command: (Start, Stop, Re= start)=E2=80=9D with a recurring schedule or a point in time execution if n= o 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, MapRed= uce, HBase, ZooKeeper, etc). Rolling restart also lets you choose which ser= vice components (Namenode, etc.) to restart. > 2. _Rebalancer_ > Rebalancer is a sample of a custom action that can be executed to initiat= e 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)