[jira] [Resolved] (YARN-4069) For long running apps (> 2 days), populate flow activity table

["Rohith Sharma K S (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/YARN-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rohith Sharma K S resolved YARN-4069.
-------------------------------------
    Resolution: Won't Fix

No activity for long time. In ATSv2 weekly call, discussed for cleaning up JIRA which are not going implement. Hence, closing the JIRA as Won't Fix. 
Feel free to reopen if still same design approach exists.  

> For long running apps (> 2 days), populate flow activity table
> --------------------------------------------------------------
>
>                 Key: YARN-4069
>                 URL: https://issues.apache.org/jira/browse/YARN-4069
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Vrushali C
>            Assignee: Varun Saxena
>            Priority: Major
>              Labels: YARN-5355
>
> YARN-4063 / YARN-3901 contain the work being done to populate the flow activity and flow run tables.
> The flow activity table is updated each time a yarn application is created and finishes. So if an application runs for more than 3 days, day1 has an entry for the flow for start time, day3 has an entry for the flow for end time but day2 has no entry for that flow. 
> Filing the jira to ensure that for long running apps, the flow activity table does get a snapshot time entered for each day that an application is running in that flow.
> It may be the case that for ALL apps (long running or not) the same update may be done in the flow activity table.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org