[jira] [Assigned] (YARN-381) Improve FS docs

[ https://issues.apache.org/jira/browse/YARN-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza reassigned YARN-381: --- Assignee: Sandy Ryza Improve FS docs --- Key: YARN-381

[jira] [Commented] (YARN-381) Improve FS docs

[ https://issues.apache.org/jira/browse/YARN-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13600981#comment-13600981 ] Sandy Ryza commented on YARN-381: - It's in megabytes. Patch coming soon will include this.

[jira] [Commented] (YARN-198) If we are navigating to Nodemanager UI from Resourcemanager,then there is not link to navigate back to Resource manager

[ https://issues.apache.org/jira/browse/YARN-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601029#comment-13601029 ] Hudson commented on YARN-198: - Integrated in Hadoop-Yarn-trunk #154 (See

[jira] [Commented] (YARN-198) If we are navigating to Nodemanager UI from Resourcemanager,then there is not link to navigate back to Resource manager

[ https://issues.apache.org/jira/browse/YARN-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601102#comment-13601102 ] Hudson commented on YARN-198: - Integrated in Hadoop-Hdfs-trunk #1343 (See

[jira] [Commented] (YARN-198) If we are navigating to Nodemanager UI from Resourcemanager,then there is not link to navigate back to Resource manager

[ https://issues.apache.org/jira/browse/YARN-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601161#comment-13601161 ] Hudson commented on YARN-198: - Integrated in Hadoop-Mapreduce-trunk #1371 (See

[jira] [Commented] (YARN-378) ApplicationMaster retry times should be set by Client

[ https://issues.apache.org/jira/browse/YARN-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601237#comment-13601237 ] Robert Joseph Evans commented on YARN-378: -- The patch looks good to me. The only

[jira] [Commented] (YARN-462) Project Parameter for Chargeback

[ https://issues.apache.org/jira/browse/YARN-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601245#comment-13601245 ] Kendall Thrapp commented on YARN-462: - Thanks for the questions and feedback. Yes,

[jira] [Commented] (YARN-379) yarn [node,application] command print logger info messages

[ https://issues.apache.org/jira/browse/YARN-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601259#comment-13601259 ] Thomas Graves commented on YARN-379: I think the approach looks fine. Did you see a way

[jira] [Updated] (YARN-460) CS user left in list of active users for the queue even when application finished

[ https://issues.apache.org/jira/browse/YARN-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated YARN-460: --- Priority: Blocker (was: Critical) CS user left in list of active users for the queue even when

[jira] [Commented] (YARN-449) HBase test failures when running against Hadoop 2

[ https://issues.apache.org/jira/browse/YARN-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601356#comment-13601356 ] Ted Yu commented on YARN-449: - Here is OS for Hadoop QA machine: Linux asf002.sp2.ygridcore.net

[jira] [Created] (YARN-473) Capacity Scheduler webpage and REST API not showing correct number of pending applications

Kendall Thrapp created YARN-473: --- Summary: Capacity Scheduler webpage and REST API not showing correct number of pending applications Key: YARN-473 URL: https://issues.apache.org/jira/browse/YARN-473

[jira] [Updated] (YARN-473) Capacity Scheduler webpage and REST API not showing correct number of pending applications

[ https://issues.apache.org/jira/browse/YARN-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kendall Thrapp updated YARN-473: Description: The Capacity Scheduler REST API

[jira] [Commented] (YARN-462) Project Parameter for Chargeback

[ https://issues.apache.org/jira/browse/YARN-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601601#comment-13601601 ] Andy Rhee commented on YARN-462: Kendall - Again, another great idea! Two things popped in

[jira] [Commented] (YARN-378) ApplicationMaster retry times should be set by Client

[ https://issues.apache.org/jira/browse/YARN-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601625#comment-13601625 ] Bikas Saha commented on YARN-378: - +1 for Vinods comments. Also, personally, I would break

[jira] [Updated] (YARN-472) MR app master deletes staging dir when sent a reboot command from the RM

[ https://issues.apache.org/jira/browse/YARN-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-472: Summary: MR app master deletes staging dir when sent a reboot command from the RM (was: MR Job falied if RM

[jira] [Updated] (YARN-472) MR app master deletes staging dir when sent a reboot command from the RM

[ https://issues.apache.org/jira/browse/YARN-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-472: Description: If the RM is restarted when the MR job is running, then it sends a reboot command to the job.

[jira] [Commented] (YARN-462) Project Parameter for Chargeback

[ https://issues.apache.org/jira/browse/YARN-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601652#comment-13601652 ] Karthik Kambatla commented on YARN-462: --- Fair points, Kendall. Thanks for the detailed

[jira] [Created] (YARN-474) CapacityScheduler does not activate applications when configuration is refreshed

Hitesh Shah created YARN-474: Summary: CapacityScheduler does not activate applications when configuration is refreshed Key: YARN-474 URL: https://issues.apache.org/jira/browse/YARN-474 Project: Hadoop

[jira] [Updated] (YARN-474) CapacityScheduler does not activate applications when configuration is refreshed

[ https://issues.apache.org/jira/browse/YARN-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-474: - Component/s: capacityscheduler CapacityScheduler does not activate applications when configuration is

[jira] [Updated] (YARN-474) CapacityScheduler does not activate applications when configuration is refreshed

[ https://issues.apache.org/jira/browse/YARN-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-474: - Target Version/s: 2.0.5-beta CapacityScheduler does not activate applications when configuration is

[jira] [Commented] (YARN-378) ApplicationMaster retry times should be set by Client

[ https://issues.apache.org/jira/browse/YARN-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601718#comment-13601718 ] Zhijie Shen commented on YARN-378: -- @Robert, if RM is supposed to inform AM about the

[jira] [Commented] (YARN-378) ApplicationMaster retry times should be set by Client

[ https://issues.apache.org/jira/browse/YARN-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601744#comment-13601744 ] Hitesh Shah commented on YARN-378: -- How about changing the AMLauncher to add the last retry

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

Hitesh Shah created YARN-475: Summary: Remove ApplicationConstants.AM_APP_ATTEMPT_ID_ENV as it is no longer set in an AM's environment Key: YARN-475 URL: https://issues.apache.org/jira/browse/YARN-475

[jira] [Created] (YARN-476) ProcfsBasedProcessTree info message confuses users

Jason Lowe created YARN-476: --- Summary: ProcfsBasedProcessTree info message confuses users Key: YARN-476 URL: https://issues.apache.org/jira/browse/YARN-476 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-378) ApplicationMaster retry times should be set by Client

[ https://issues.apache.org/jira/browse/YARN-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601770#comment-13601770 ] Bikas Saha commented on YARN-378: - How about getting an estimate on MAPREDUCE-5062 effort

[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=13601810#comment-13601810 ] Zhijie Shen commented on YARN-475: -- ApplicationConstants.AM_APP_ATTEMPT_ID_ENV seems to be

[jira] [Commented] (YARN-378) ApplicationMaster retry times should be set by Client

[ https://issues.apache.org/jira/browse/YARN-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601813#comment-13601813 ] Bikas Saha commented on YARN-378: - If its too much work in the MR AM then we could set the

[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=13601838#comment-13601838 ] Bikas Saha commented on YARN-475: - Even when we remove it - is there some helper lib/api to

[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=13601883#comment-13601883 ] Hitesh Shah commented on YARN-475: -- {code} // get containerIdStr from environment

[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-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=13601905#comment-13601905 ] Hitesh Shah commented on YARN-475: -- Both DistributedShell and UnmanagedAM use it currently

[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-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=13601952#comment-13601952 ] Siddharth Seth commented on YARN-226: - bq. The Giraph to YARN port assumes giraph tasks

[jira] [Updated] (YARN-474) CapacityScheduler does not activate applications when configuration is refreshed

[ https://issues.apache.org/jira/browse/YARN-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated YARN-474: --- Target Version/s: 0.23.7, 2.0.5-beta (was: 2.0.5-beta) Affects Version/s: 2.0.3-alpha

[jira] [Assigned] (YARN-440) Flatten RegisterNodeManagerResponse

[ https://issues.apache.org/jira/browse/YARN-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong reassigned YARN-440: -- Assignee: Xuan Gong Flatten RegisterNodeManagerResponse ---

[jira] [Assigned] (YARN-439) Flatten NodeHeartbeatResponse

[ https://issues.apache.org/jira/browse/YARN-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong reassigned YARN-439: -- Assignee: Xuan Gong Flatten NodeHeartbeatResponse -

[jira] [Commented] (YARN-71) Ensure/confirm that the NodeManager cleans up local-dirs on restart

[ https://issues.apache.org/jira/browse/YARN-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13602042#comment-13602042 ] Siddharth Seth commented on YARN-71: Comments on the latest patch. - timestamp can moce

[jira] [Comment Edited] (YARN-71) Ensure/confirm that the NodeManager cleans up local-dirs on restart

[ https://issues.apache.org/jira/browse/YARN-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13602042#comment-13602042 ] Siddharth Seth edited comment on YARN-71 at 3/14/13 5:20 AM: -

[jira] [Commented] (YARN-378) ApplicationMaster retry times should be set by Client

[ https://issues.apache.org/jira/browse/YARN-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13602055#comment-13602055 ] Vinod Kumar Vavilapalli commented on YARN-378: -- +1 for maxAppAttempts naming.