Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Thu, 3 Sep 2015 11:58:47 +0000 (UTC)
From: "Sunil G (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12838426.1434534440000.245943.1441281527068@Atlassian.JIRA>
In-Reply-To: <JIRA.12838426.1434534440000@Atlassian.JIRA>
References: <JIRA.12838426.1434534440000@Atlassian.JIRA>
 <JIRA.12838426.1434534440661@arcas>
Subject: [jira] [Commented] (YARN-3813) Support Application timeout feature
 in YARN.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sunil G commented on YARN-3813:
-------------------------------

As I see this, the trigger point to identify an application to be Timedout (or killed) is based on the elapsed time (calculated from its submission time). If an application can be registered to RMAppTimeOutMonitor after submission, I feel we may need not have to worry about internal state. 

> Support Application timeout feature in YARN. 
> ---------------------------------------------
>
>                 Key: YARN-3813
>                 URL: https://issues.apache.org/jira/browse/YARN-3813
>             Project: Hadoop YARN
>          Issue Type: New Feature
>          Components: scheduler
>            Reporter: nijel
>            Assignee: nijel
>         Attachments: 0001-YARN-3813.patch, YARN Application Timeout .pdf
>
>
> It will be useful to support Application Timeout in YARN. Some use cases are not worried about the output of the applications if the application is not completed in a specific time. 
> *Background:*
> The requirement is to show the CDR statistics of last few  minutes, say for every 5 minutes. The same Job will run continuously with different dataset.
> So one job will be started in every 5 minutes. The estimate time for this task is 2 minutes or lesser time. 
> If the application is not completing in the given time the output is not useful.
> *Proposal*
> So idea is to support application timeout, with which timeout parameter is given while submitting the job. 
> Here, user is expecting to finish (complete or kill) the application in the given time.
> One option for us is to move this logic to Application client (who submit the job). 
> But it will be nice if it can be generic logic and can make more robust.
> Kindly provide your suggestions/opinion on this feature. If it sounds good, i will update the design doc and prototype patch


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