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

Jonathan Hung commented on YARN-9438:
-------------------------------------

002 changes:
 * Use the same ApplicationStateData constructor in RMAppImpl as in 
RMStateStore#storeNewApplication
 * Fix TestRMRestart#testRMRestartWaitForPreviousSucceededAttempt: first call 
to updateApplicationStateInternal should not be skipped (first one is saving 
launchTime), second one should be skipped
 * Fix TestRMRestart#testClientRetryOnKillingApplication: similar to above. 
TestMemoryRMStateStore's {{count}} is incremented when storing launchTime, so 
increment the counts in this test accordingly
 * Fix TestRMRestart#testRMRestartOnMissingAttempts: storing launchTime creates 
a new ApplicationStateData in memory state store, hence move the app state 
getter after the attempts have been launched

 

> launchTime not written to state store for running applications
> --------------------------------------------------------------
>
>                 Key: YARN-9438
>                 URL: https://issues.apache.org/jira/browse/YARN-9438
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.10.0
>            Reporter: Jonathan Hung
>            Assignee: Jonathan Hung
>            Priority: Major
>         Attachments: YARN-9438.001.patch, YARN-9438.002.patch
>
>
> launchTime is only saved to state store after application finishes, so if 
> restart happens, any running applications will have launchTime set as -1 
> (since this is the default timestamp of the recovery event).



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

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

Reply via email to