Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@falcon.apache.org
Date: Mon, 25 Jan 2016 10:38:39 +0000 (UTC)
From: "Pallavi Rao (JIRA)" <jira@apache.org>
To: dev@falcon.incubator.apache.org
Message-ID: <JIRA.12933772.1453716967000.199139.1453718319850@Atlassian.JIRA>
In-Reply-To: <JIRA.12933772.1453716967000@Atlassian.JIRA>
References: <JIRA.12933772.1453716967000@Atlassian.JIRA>
 <JIRA.12933772.1453716967826@arcas>
Subject: [jira] [Commented] (FALCON-1773) Allow falcon CLI to set endtime
 for falcon process
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/FALCON-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115019#comment-15115019 ] 

Pallavi Rao commented on FALCON-1773:
-------------------------------------

[~sanjeevtripurari], basically, I think this is what you are trying to achieve :
1. Pause a process with a specified pause time. So, no more instances get scheduled after the pause time.
2. Update/Touch the process definition, workflows, jars, etc.
3. Un-pause the entity with a new time. That way, the new instances start from the time specified.

> Allow falcon CLI to set endtime for falcon process
> --------------------------------------------------
>
>                 Key: FALCON-1773
>                 URL: https://issues.apache.org/jira/browse/FALCON-1773
>             Project: Falcon
>          Issue Type: Improvement
>            Reporter: Sanjeev T
>            Assignee: Pallavi Rao
>
> * Problem
> We often come across situation, when falcon process needs change, like
> * workflow change
> * jar change
> in the current status, 
> The jar change during that time causes falcon instance to get killed.
> the next falcon instance may pick the new change, but we might want to start with different time.
> To set endtime for falcon process we need to pull out the definition set the endtime submit it, and then after the change re-submit it we new start time
> If we can set endtime to falcon process, and let the process come to EOL.
> do the change, 
> and update falcon process with new start time, it will be safer and we will be sure of the new changes taking place from the specific time, it can be also previous or current time, this is too much of manual process and change in xml file.
> Requirement
> * Allow falcon cli to setendtime to the process
> * do the copy of workflow/jar or what ever changes
> * let user submit/update the process with new start time


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)