[jira] [Updated] (YARN-592) Container logs lost for the application when NM gets restarted
[ https://issues.apache.org/jira/browse/YARN-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj K updated YARN-592: --- Attachment: YARN-592.patch > Container logs lost for the application when NM gets restarted > -- > > Key: YARN-592 > URL: https://issues.apache.org/jira/browse/YARN-592 > Project: Hadoop YARN > Issue Type: Bug > Components: nodemanager >Affects Versions: 2.0.1-alpha, 2.0.3-alpha >Reporter: Devaraj K >Assignee: Devaraj K >Priority: Critical > Attachments: YARN-592.patch > > > While running a big job if the NM goes down due to some reason and comes > back, it will do the log aggregation for the newly launched containers and > deletes all the containers for the application. This case we don't get the > container logs from HDFS or local for the containers which are launched > before restart and completed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (YARN-592) Container logs lost for the application when NM gets restarted
[ https://issues.apache.org/jira/browse/YARN-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-592: - Target Version/s: 2.0.5-beta Setting target version to be 2.0.05-beta. Devaraj, I see you assigned it to yourselves, I suppose you have cycles to get this done in time for 2.0.5-beta. Let me know otherwise, thanks. > Container logs lost for the application when NM gets restarted > -- > > Key: YARN-592 > URL: https://issues.apache.org/jira/browse/YARN-592 > Project: Hadoop YARN > Issue Type: Bug > Components: nodemanager >Affects Versions: 2.0.1-alpha, 2.0.3-alpha >Reporter: Devaraj K >Assignee: Devaraj K >Priority: Critical > > While running a big job if the NM goes down due to some reason and comes > back, it will do the log aggregation for the newly launched containers and > deletes all the containers for the application. This case we don't get the > container logs from HDFS or local for the containers which are launched > before restart and completed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (YARN-592) Container logs lost for the application when NM gets restarted
[ https://issues.apache.org/jira/browse/YARN-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj K updated YARN-592: --- Priority: Critical (was: Major) > Container logs lost for the application when NM gets restarted > -- > > Key: YARN-592 > URL: https://issues.apache.org/jira/browse/YARN-592 > Project: Hadoop YARN > Issue Type: Bug > Components: nodemanager >Affects Versions: 2.0.1-alpha, 2.0.3-alpha >Reporter: Devaraj K >Assignee: Devaraj K >Priority: Critical > > While running a big job if the NM goes down due to some reason and comes > back, it will do the log aggregation for the newly launched containers and > deletes all the containers for the application. This case we don't get the > container logs from HDFS or local for the containers which are launched > before restart and completed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
