[jira] [Updated] (YARN-437) Update documentation of Writing Yarn Applications to match current best practices

[ https://issues.apache.org/jira/browse/YARN-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Reisman updated YARN-437: - Attachment: YARN-437-3.patch Added a couple small points I missed before, and fixed (I hope) some

[jira] [Commented] (YARN-477) MiniYARNCluster: When container executor script fails to launch App Master, NM logs error, but Client doesn't get signaled to kill the job

[ https://issues.apache.org/jira/browse/YARN-477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13604440#comment-13604440 ] Eli Reisman commented on YARN-477: -- Sorry, tried to recreate this today and am not seeing

[jira] [Commented] (YARN-226) Log aggregation should not assume an AppMaster will have containerId 1

[ https://issues.apache.org/jira/browse/YARN-226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13603527#comment-13603527 ] Eli Reisman commented on YARN-226: -- Hmm. It would not be impossible to ask for one

[jira] [Commented] (YARN-226) Log aggregation should not assume an AppMaster will have containerId 1

[ https://issues.apache.org/jira/browse/YARN-226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13602614#comment-13602614 ] Eli Reisman commented on YARN-226: -- Hmm, that stirs up some trouble. Giraph tasks may or

[jira] [Commented] (YARN-477) When default container executor fails right away, at the CLI launching our App Master, Client doesn't always get the signal to kill the job

[ https://issues.apache.org/jira/browse/YARN-477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13602892#comment-13602892 ] Eli Reisman commented on YARN-477: -- Duh. Too many issues fixed all at once, they are all

[jira] [Commented] (YARN-477) When default container executor fails right away, at the CLI launching our App Master, Client doesn't always get the signal to kill the job

[ https://issues.apache.org/jira/browse/YARN-477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13602895#comment-13602895 ] Eli Reisman commented on YARN-477: -- nodemanager log for MiniYARNCluster DID get a log

[jira] [Updated] (YARN-477) MiniYARNCluster: When container executor script fails to launch App Master, NM logs error, but Client doesn't get signaled to kill the job

[ https://issues.apache.org/jira/browse/YARN-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Reisman updated YARN-477: - Summary: MiniYARNCluster: When container executor script fails to launch App Master, NM logs error, but

[jira] [Commented] (YARN-475) Remove ApplicationConstants.AM_APP_ATTEMPT_ID_ENV as it is no longer set in an AM's environment

[ https://issues.apache.org/jira/browse/YARN-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601897#comment-13601897 ] Eli Reisman commented on YARN-475: -- Thanks, I was just going to ask this. So the

[jira] [Commented] (YARN-437) Update documentation of Writing Yarn applications to match current best practices

[ https://issues.apache.org/jira/browse/YARN-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601913#comment-13601913 ] Eli Reisman commented on YARN-437: -- I agree. Its painful to wait but this won't get done

[jira] [Commented] (YARN-367) Exception when yarn.nodemanager.local-dirs is not explicitly set

[ https://issues.apache.org/jira/browse/YARN-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13568914#comment-13568914 ] Eli Reisman commented on YARN-367: -- This is great, I was actually about to do the same