[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-tabpanel&focusedCommentId=13599778#comment-13599778 ] Hadoop QA commented on YARN-378: {color:green}+1 overall{color}. Here are the results of te

[jira] [Commented] (YARN-449) MRAppMaster classpath not set properly for unit tests in downstream projects

[ https://issues.apache.org/jira/browse/YARN-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13599733#comment-13599733 ] Ted Yu commented on YARN-449: - Test failure couldn't be reproduced on Mac. On flubber machine,

[jira] [Updated] (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:all-tabpanel ] Zhijie Shen updated YARN-378: - Attachment: YARN-378_6.patch Fix the broken test and the javadoc warn. > ApplicationMaster

[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-tabpanel&focusedCommentId=13599724#comment-13599724 ] Hadoop QA commented on YARN-198: {color:red}-1 overall{color}. Here are the results of test

[jira] [Updated] (YARN-449) MRAppMaster classpath not set properly for unit tests in downstream projects

[ https://issues.apache.org/jira/browse/YARN-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated YARN-449: Attachment: minimr_randomdir-branch2.txt randomize directories generated when using MiniMRCluster.

[jira] [Commented] (YARN-449) MRAppMaster classpath not set properly for unit tests in downstream projects

[ https://issues.apache.org/jira/browse/YARN-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13599719#comment-13599719 ] Siddharth Seth commented on YARN-449: - Ted, are all these tests passing against 2.0.2-al

[jira] [Updated] (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:all-tabpanel ] jian he updated YARN-198: - Attachment: YARN-198.patch > If we are navigating to Nodemanager UI from Resourcemanager,then there is not > l

[jira] [Updated] (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:all-tabpanel ] jian he updated YARN-198: - Attachment: (was: YARN-198.patch) > If we are navigating to Nodemanager UI from Resourcemanager,then there

[jira] [Commented] (YARN-237) Refreshing the RM page forgets how many rows I had in my Datatables

[ https://issues.apache.org/jira/browse/YARN-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13599664#comment-13599664 ] Hadoop QA commented on YARN-237: {color:red}-1 overall{color}. Here are the results of test

[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-tabpanel&focusedCommentId=13599622#comment-13599622 ] Siddharth Seth commented on YARN-71: Thanks for the patches Xuan. Couple of comments on t

[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-tabpanel&focusedCommentId=13599552#comment-13599552 ] Hadoop QA commented on YARN-378: {color:red}-1 overall{color}. Here are the results of test

[jira] [Updated] (YARN-237) Refreshing the RM page forgets how many rows I had in my Datatables

[ https://issues.apache.org/jira/browse/YARN-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jian he updated YARN-237: - Attachment: YARN-237.v4.patch > Refreshing the RM page forgets how many rows I had in my Datatables > -

[jira] [Commented] (YARN-237) Refreshing the RM page forgets how many rows I had in my Datatables

[ https://issues.apache.org/jira/browse/YARN-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13599544#comment-13599544 ] jian he commented on YARN-237: -- thanks for your comment Robert, updated the patch.

[jira] [Created] (YARN-467) Jobs fail during resource localization when directories in file cache reaches to unix directory limit for public cache

omkar vinit joshi created YARN-467: -- Summary: Jobs fail during resource localization when directories in file cache reaches to unix directory limit for public cache Key: YARN-467 URL: https://issues.apache.org/ji

[jira] [Updated] (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:all-tabpanel ] Zhijie Shen updated YARN-378: - Attachment: YARN-378_5.patch In the newest patch, I've addressed @Robert's comments, which is setting numM

[jira] [Updated] (YARN-459) DefaultContainerExecutor doesn't log stderr from container launch

[ https://issues.apache.org/jira/browse/YARN-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-459: Description: The DefaultContainerExecutor does not log stderr or add it to the diagnostics message it someth

[jira] [Commented] (YARN-24) Nodemanager fails to start if log aggregation enabled and namenode unavailable

[ https://issues.apache.org/jira/browse/YARN-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13599490#comment-13599490 ] Alejandro Abdelnur commented on YARN-24: The approach looks good. Possible to have a

[jira] [Commented] (YARN-417) Add a poller that allows the AM to receive notifications when it is assigned containers

[ https://issues.apache.org/jira/browse/YARN-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13599479#comment-13599479 ] Sandy Ryza commented on YARN-417: - I'm not sure what the problem with eclipse:eclipse is. I

[jira] [Created] (YARN-466) Slave hostname mismatches in ResourceManager/Scheduler

Roger Hoover created YARN-466: - Summary: Slave hostname mismatches in ResourceManager/Scheduler Key: YARN-466 URL: https://issues.apache.org/jira/browse/YARN-466 Project: Hadoop YARN Issue Type:

[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-tabpanel&focusedCommentId=13599457#comment-13599457 ] Hadoop QA commented on YARN-71: --- {color:red}-1 overall{color}. Here are the results of testing

[jira] [Updated] (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:all-tabpanel ] Xuan Gong updated YARN-71: -- Attachment: YARN-71.6.patch > Ensure/confirm that the NodeManager cleans up local-dirs on restart > --

[jira] [Commented] (YARN-196) Nodemanager if started before starting Resource manager is getting shutdown.But if both RM and NM are started and then after if RM is going down,NM is retrying for the RM

[ https://issues.apache.org/jira/browse/YARN-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13599425#comment-13599425 ] Hadoop QA commented on YARN-196: {color:red}-1 overall{color}. Here are the results of test

[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-tabpanel&focusedCommentId=13599423#comment-13599423 ] Hadoop QA commented on YARN-71: --- {color:red}-1 overall{color}. Here are the results of testing

[jira] [Updated] (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:all-tabpanel ] Xuan Gong updated YARN-71: -- Attachment: YARN-71.5.patch > Ensure/confirm that the NodeManager cleans up local-dirs on restart > --

[jira] [Updated] (YARN-196) Nodemanager if started before starting Resource manager is getting shutdown.But if both RM and NM are started and then after if RM is going down,NM is retrying for the RM.

[ https://issues.apache.org/jira/browse/YARN-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-196: --- Attachment: YARN-196.12.patch > Nodemanager if started before starting Resource manager is getting > shutd

[jira] [Commented] (YARN-18) Make locatlity in YARN's container assignment and task scheduling pluggable for other deployment topology

[ https://issues.apache.org/jira/browse/YARN-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13599383#comment-13599383 ] Luke Lu commented on YARN-18: - Preliminary comments: # We should use net.topology.nodegroup.aware

[jira] [Commented] (YARN-417) Add a poller that allows the AM to receive notifications when it is assigned containers

[ https://issues.apache.org/jira/browse/YARN-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13599380#comment-13599380 ] Hadoop QA commented on YARN-417: {color:red}-1 overall{color}. Here are the results of test

[jira] [Updated] (YARN-417) Add a poller that allows the AM to receive notifications when it is assigned containers

[ https://issues.apache.org/jira/browse/YARN-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-417: Attachment: YARN-417-4.patch Updated patch uses interrupt to fix the deadlock that was causing the test to f

[jira] [Resolved] (YARN-464) RM should inform AM how many AM retries it has

[ https://issues.apache.org/jira/browse/YARN-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-464. -- Resolution: Duplicate > RM should inform AM how many AM retries it has >

[jira] [Reopened] (YARN-464) RM should inform AM how many AM retries it has

[ https://issues.apache.org/jira/browse/YARN-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reopened YARN-464: -- > RM should inform AM how many AM retries it has > --

[jira] [Resolved] (YARN-464) RM should inform AM how many AM retries it has

[ https://issues.apache.org/jira/browse/YARN-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen resolved YARN-464. -- Resolution: Won't Fix > RM should inform AM how many AM retries it has >

[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-tabpanel&focusedCommentId=13599297#comment-13599297 ] Zhijie Shen commented on YARN-378: -- Sure, I can merge the two patches together and submit o

[jira] [Commented] (YARN-464) RM should inform AM how many AM retries it has

[ https://issues.apache.org/jira/browse/YARN-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13599299#comment-13599299 ] Zhijie Shen commented on YARN-464: -- Will be fixed together in YARN-378. >

[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-tabpanel&focusedCommentId=13599240#comment-13599240 ] Robert Joseph Evans commented on YARN-378: -- I am perfectly fine with that. It seem

[jira] [Commented] (YARN-237) Refreshing the RM page forgets how many rows I had in my Datatables

[ https://issues.apache.org/jira/browse/YARN-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13599236#comment-13599236 ] Robert Joseph Evans commented on YARN-237: -- Sorry to keep adding more things in her

[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-tabpanel&focusedCommentId=13599221#comment-13599221 ] Hitesh Shah commented on YARN-378: -- @Zhijie, @Robert - does it makes sense to split this ou

[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-tabpanel&focusedCommentId=13599215#comment-13599215 ] Robert Joseph Evans commented on YARN-378: -- The patch looks a lot better and thanks

[jira] [Commented] (YARN-449) MRAppMaster classpath not set properly for unit tests in downstream projects

[ https://issues.apache.org/jira/browse/YARN-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13599168#comment-13599168 ] Ted Yu commented on YARN-449: - Under hbase-server/target/org.apache.hadoop.mapred.MiniMRCluster,

[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-tabpanel&focusedCommentId=13599091#comment-13599091 ] Xuan Gong commented on YARN-71: --- The approach I am using: 1. rename the folder (local files are

[jira] [Updated] (YARN-464) RM should inform AM how many AM retries it has

[ https://issues.apache.org/jira/browse/YARN-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-464: Summary: RM should inform AM how many AM retries it has (was: RM should inform AM how many AM retires it has

[jira] [Commented] (YARN-196) Nodemanager if started before starting Resource manager is getting shutdown.But if both RM and NM are started and then after if RM is going down,NM is retrying for the RM

[ https://issues.apache.org/jira/browse/YARN-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13599024#comment-13599024 ] Hadoop QA commented on YARN-196: {color:green}+1 overall{color}. Here are the results of te

[jira] [Updated] (YARN-196) Nodemanager if started before starting Resource manager is getting shutdown.But if both RM and NM are started and then after if RM is going down,NM is retrying for the RM.

[ https://issues.apache.org/jira/browse/YARN-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-196: --- Attachment: YARN-196.11.patch > Nodemanager if started before starting Resource manager is getting > shutd

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13598814#comment-13598814 ] Thomas Graves commented on YARN-460: Yeah I think that is a good idea. Perhaps somethin

[jira] [Commented] (YARN-465) fix coverage org.apache.hadoop.yarn.server.webproxy

[ https://issues.apache.org/jira/browse/YARN-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13598784#comment-13598784 ] Hadoop QA commented on YARN-465: {color:green}+1 overall{color}. Here are the results of te

[jira] [Commented] (YARN-465) fix coverage org.apache.hadoop.yarn.server.webproxy

[ https://issues.apache.org/jira/browse/YARN-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13598777#comment-13598777 ] Dennis Y commented on YARN-465: --- Patch contains new file "hadoop-yarn-project/hadoop-yarn/had

[jira] [Updated] (YARN-465) fix coverage org.apache.hadoop.yarn.server.webproxy

[ https://issues.apache.org/jira/browse/YARN-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Gorshkov updated YARN-465: -- Description: fix coverage org.apache.hadoop.yarn.server.webproxy patch YARN-465-trunk.patch for

[jira] [Created] (YARN-465) fix coverage org.apache.hadoop.yarn.server.webproxy

Aleksey Gorshkov created YARN-465: - Summary: fix coverage org.apache.hadoop.yarn.server.webproxy Key: YARN-465 URL: https://issues.apache.org/jira/browse/YARN-465 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-465) fix coverage org.apache.hadoop.yarn.server.webproxy

[ https://issues.apache.org/jira/browse/YARN-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Gorshkov updated YARN-465: -- Attachment: YARN-465-trunk.patch YARN-465-branch-2.patch YARN-465-

[jira] [Updated] (YARN-465) fix coverage org.apache.hadoop.yarn.server.webproxy

[ https://issues.apache.org/jira/browse/YARN-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Gorshkov updated YARN-465: -- Description: fix coverage org.apache.hadoop.yarn.server.webproxy was:fix coverage org.apach