[jira] [Commented] (YARN-1188) The context of QueueMetrics becomes 'default' when using FairScheduler

[ https://issues.apache.org/jira/browse/YARN-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13774336#comment-13774336 ] Sandy Ryza commented on YARN-1188: -- +1 The context of QueueMetrics

[jira] [Updated] (YARN-1188) The context of QueueMetrics becomes 'default' when using FairScheduler

[ https://issues.apache.org/jira/browse/YARN-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1188: - Assignee: Akira AJISAKA The context of QueueMetrics becomes 'default' when using FairScheduler

[jira] [Commented] (YARN-1188) The context of QueueMetrics becomes 'default' when using FairScheduler

[ https://issues.apache.org/jira/browse/YARN-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13774344#comment-13774344 ] Sandy Ryza commented on YARN-1188: -- I just committed this to trunk and branch-2. Thanks

[jira] [Commented] (YARN-1188) The context of QueueMetrics becomes 'default' when using FairScheduler

[ https://issues.apache.org/jira/browse/YARN-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13774350#comment-13774350 ] Hudson commented on YARN-1188: -- SUCCESS: Integrated in Hadoop-trunk-Commit #4451 (See

[jira] [Commented] (YARN-1188) The context of QueueMetrics becomes 'default' when using FairScheduler

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

[jira] [Commented] (YARN-1188) The context of QueueMetrics becomes 'default' when using FairScheduler

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

[jira] [Commented] (YARN-1188) The context of QueueMetrics becomes 'default' when using FairScheduler

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

[jira] [Commented] (YARN-1041) RM to bind and notify a restarted AM of existing containers

[ https://issues.apache.org/jira/browse/YARN-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13774539#comment-13774539 ] Steve Loughran commented on YARN-1041: -- I'd add that discarding outstanding requests

[jira] [Updated] (YARN-1226) ipv4 and ipv6 affect job data locality

[ https://issues.apache.org/jira/browse/YARN-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kaibo Zhou updated YARN-1226: - Description: When I run a mapreduce job which use TableInputFormat to scan a hbase table on yarn cluser

[jira] [Updated] (YARN-1226) ipv4 and ipv6 affect job data locality

[ https://issues.apache.org/jira/browse/YARN-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kaibo Zhou updated YARN-1226: - Description: When I run a mapreduce job which use TableInputFormat to scan a hbase table on yarn cluser

[jira] [Updated] (YARN-1226) ipv4 and ipv6 affect job data locality

[ https://issues.apache.org/jira/browse/YARN-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kaibo Zhou updated YARN-1226: - Description: When I run a mapreduce job which use TableInputFormat to scan a hbase table on yarn cluser

[jira] [Updated] (YARN-1226) ipv4 and ipv6 affect job data locality

[ https://issues.apache.org/jira/browse/YARN-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kaibo Zhou updated YARN-1226: - Description: When I run a mapreduce job which use TableInputFormat to scan a hbase table on yarn cluser

[jira] [Created] (YARN-1226) ipv4 and ipv6 affect job data locality

Kaibo Zhou created YARN-1226: Summary: ipv4 and ipv6 affect job data locality Key: YARN-1226 URL: https://issues.apache.org/jira/browse/YARN-1226 Project: Hadoop YARN Issue Type: Improvement

[jira] [Updated] (YARN-1226) ipv4 and ipv6 affect job data locality

[ https://issues.apache.org/jira/browse/YARN-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kaibo Zhou updated YARN-1226: - Description: When I run a mapreduce job which use TableInputFormat to scan a hbase table on yarn cluser

[jira] [Updated] (YARN-1226) ipv4 and ipv6 affect job data locality

[ https://issues.apache.org/jira/browse/YARN-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kaibo Zhou updated YARN-1226: - Description: When I run a mapreduce job which use TableInputFormat to scan a hbase table on yarn cluser

[jira] [Updated] (YARN-1226) ipv4 and ipv6 lead to poor data locality

[ https://issues.apache.org/jira/browse/YARN-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kaibo Zhou updated YARN-1226: - Priority: Major (was: Minor) ipv4 and ipv6 lead to poor data locality

[jira] [Updated] (YARN-1226) ipv4 and ipv6 lead to poor data locality

[ https://issues.apache.org/jira/browse/YARN-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kaibo Zhou updated YARN-1226: - Summary: ipv4 and ipv6 lead to poor data locality (was: ipv4 and ipv6 affect job data locality)

[jira] [Created] (YARN-1227) Update Single Cluster doc to use yarn.resourcemanager.hostname

Sandy Ryza created YARN-1227: Summary: Update Single Cluster doc to use yarn.resourcemanager.hostname Key: YARN-1227 URL: https://issues.apache.org/jira/browse/YARN-1227 Project: Hadoop YARN

[jira] [Commented] (YARN-1204) Need to add https port related property in Yarn

[ https://issues.apache.org/jira/browse/YARN-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13774742#comment-13774742 ] Vinod Kumar Vavilapalli commented on YARN-1204: --- Quickly looked at the patch.

[jira] [Commented] (YARN-1221) With Fair Scheduler, reserved MB reported in RM web UI increases indefinitely

[ https://issues.apache.org/jira/browse/YARN-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13774765#comment-13774765 ] Siqi Li commented on YARN-1221: --- According to the fairsheduler log, 2013-09-23 17:32:30,593

[jira] [Updated] (YARN-1157) ResourceManager UI has invalid tracking URL link for distributed shell application

[ https://issues.apache.org/jira/browse/YARN-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1157: Attachment: YARN-1157.3.patch Update patch based on latest trunk ResourceManager UI has

[jira] [Commented] (YARN-1227) Update Single Cluster doc to use yarn.resourcemanager.hostname

[ https://issues.apache.org/jira/browse/YARN-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13774812#comment-13774812 ] Karthik Kambatla commented on YARN-1227: This is related to HA-specific

[jira] [Commented] (YARN-1222) Make improvements in ZKRMStateStore for fencing

[ https://issues.apache.org/jira/browse/YARN-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13774658#comment-13774658 ] Karthik Kambatla commented on YARN-1222: Another approach we could take is let the

[jira] [Created] (YARN-1228) Don't allow other file than fair-scheduler.xml to be Fair Scheduler allocations file

Sandy Ryza created YARN-1228: Summary: Don't allow other file than fair-scheduler.xml to be Fair Scheduler allocations file Key: YARN-1228 URL: https://issues.apache.org/jira/browse/YARN-1228 Project:

[jira] [Updated] (YARN-1188) The context of QueueMetrics becomes 'default' when using FairScheduler

[ https://issues.apache.org/jira/browse/YARN-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1188: - Assignee: Tsuyoshi OZAWA The context of QueueMetrics becomes 'default' when using FairScheduler

[jira] [Updated] (YARN-1227) Update Single Cluster doc to use yarn.resourcemanager.hostname

[ https://issues.apache.org/jira/browse/YARN-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1227: - Labels: newbie (was: ) Update Single Cluster doc to use yarn.resourcemanager.hostname

[jira] [Assigned] (YARN-1229) Shell$ExitCodeException could happen if AM fails to start

[ https://issues.apache.org/jira/browse/YARN-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong reassigned YARN-1229: --- Assignee: Xuan Gong Shell$ExitCodeException could happen if AM fails to start

[jira] [Commented] (YARN-819) ResourceManager and NodeManager should check for a minimum allowed version

[ https://issues.apache.org/jira/browse/YARN-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13775697#comment-13775697 ] Robert Parker commented on YARN-819: Jon, Thanks for the review and nice catch on

[jira] [Commented] (YARN-451) Add more metrics to RM page

[ https://issues.apache.org/jira/browse/YARN-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13775700#comment-13775700 ] Jason Lowe commented on YARN-451: - Is knowing how big an application might get in the future

[jira] [Commented] (YARN-1204) Need to add https port related property in Yarn

[ https://issues.apache.org/jira/browse/YARN-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13775703#comment-13775703 ] Omkar Vinit Joshi commented on YARN-1204: - Thanks vinod for the review.. bq.

[jira] [Comment Edited] (YARN-451) Add more metrics to RM page

[ https://issues.apache.org/jira/browse/YARN-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13775700#comment-13775700 ] Jason Lowe edited comment on YARN-451 at 9/23/13 9:59 PM: -- Is

[jira] [Commented] (YARN-1229) Shell$ExitCodeException could happen if AM fails to start

[ https://issues.apache.org/jira/browse/YARN-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13775711#comment-13775711 ] Xuan Gong commented on YARN-1229: - [~vinodkv], [~bikassaha], [~hitesh], [~sseth], [~jlowe],

[jira] [Commented] (YARN-1215) Yarn URL should include userinfo

[ https://issues.apache.org/jira/browse/YARN-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13775718#comment-13775718 ] shanyu zhao commented on YARN-1215: --- Looks good to me overall. But I think the best fix

[jira] [Commented] (YARN-1199) Make NM/RM Versions Available

[ https://issues.apache.org/jira/browse/YARN-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13775724#comment-13775724 ] Robert Parker commented on YARN-1199: - +1 non-binding Make NM/RM

[jira] [Commented] (YARN-1157) ResourceManager UI has invalid tracking URL link for distributed shell application

[ https://issues.apache.org/jira/browse/YARN-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13775730#comment-13775730 ] Jian He commented on YARN-1157: --- For the following code, we may create a common function for

[jira] [Assigned] (YARN-1210) During RM restart, RM should start a new attempt only when previous attempt exits for real

[ https://issues.apache.org/jira/browse/YARN-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He reassigned YARN-1210: - Assignee: Jian He (was: Vinod Kumar Vavilapalli) During RM restart, RM should start a new attempt

[jira] [Updated] (YARN-955) [YARN-321] History Service should create the RPC server and wire it to HistoryStorage

[ https://issues.apache.org/jira/browse/YARN-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-955: --- Attachment: YARN-955-1.patch Attaching patch. Thanks, Mayank [YARN-321] History

[jira] [Updated] (YARN-1228) Clean up Fair Scheduler configuration loading

[ https://issues.apache.org/jira/browse/YARN-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1228: - Summary: Clean up Fair Scheduler configuration loading (was: Don't allow other file than

[jira] [Commented] (YARN-1210) During RM restart, RM should start a new attempt only when previous attempt exits for real

[ https://issues.apache.org/jira/browse/YARN-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13775762#comment-13775762 ] Jian He commented on YARN-1210: --- Also, NM needs to be changed to at least report back the

[jira] [Updated] (YARN-1228) Clean up Fair Scheduler configuration loading

[ https://issues.apache.org/jira/browse/YARN-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1228: - Attachment: YARN-1228.patch Clean up Fair Scheduler configuration loading

[jira] [Updated] (YARN-1228) Clean up Fair Scheduler configuration loading

[ https://issues.apache.org/jira/browse/YARN-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1228: - Description: Currently the Fair Scheduler is configured in two ways * An allocations file that has a

[jira] [Commented] (YARN-1228) Clean up Fair Scheduler configuration loading

[ https://issues.apache.org/jira/browse/YARN-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13775769#comment-13775769 ] Sandy Ryza commented on YARN-1228: -- Existing tests verify that absolute paths and not

[jira] [Commented] (YARN-955) [YARN-321] History Service should create the RPC server and wire it to HistoryStorage

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

[jira] [Commented] (YARN-1228) Clean up Fair Scheduler configuration loading

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

[jira] [Updated] (YARN-1214) Register ClientToken MasterKey in SecretManager after it is saved

[ https://issues.apache.org/jira/browse/YARN-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-1214: -- Attachment: YARN-1214.5.patch New patch added the comments. Register ClientToken MasterKey in

[jira] [Commented] (YARN-1157) ResourceManager UI has invalid tracking URL link for distributed shell application

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

[jira] [Commented] (YARN-1068) Add admin support for HA operations

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

[jira] [Updated] (YARN-49) Improve distributed shell application to work on a secure cluster

[ https://issues.apache.org/jira/browse/YARN-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-49: Attachment: YARN-49-20130923.3.txt Straight forward patch to add security - Client

[jira] [Updated] (YARN-1068) Add admin support for HA operations

[ https://issues.apache.org/jira/browse/YARN-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1068: --- Attachment: yarn-1068-6.patch Minor update to the patch - RMHAProtocolService should continue

[jira] [Commented] (YARN-819) ResourceManager and NodeManager should check for a minimum allowed version

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

[jira] [Created] (YARN-1230) Fair scheduler aclSubmitApps does not handle acls with only groups

Sandy Ryza created YARN-1230: Summary: Fair scheduler aclSubmitApps does not handle acls with only groups Key: YARN-1230 URL: https://issues.apache.org/jira/browse/YARN-1230 Project: Hadoop YARN

[jira] [Created] (YARN-1231) Fix test cases that will hit max- am-used-resources-percent limit after YARN-276

Nemon Lou created YARN-1231: --- Summary: Fix test cases that will hit max- am-used-resources-percent limit after YARN-276 Key: YARN-1231 URL: https://issues.apache.org/jira/browse/YARN-1231 Project: Hadoop

[jira] [Commented] (YARN-1157) ResourceManager UI has invalid tracking URL link for distributed shell application

[ https://issues.apache.org/jira/browse/YARN-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13775906#comment-13775906 ] Xuan Gong commented on YARN-1157: - bq.For the following code, we may create a common

[jira] [Updated] (YARN-1157) ResourceManager UI has invalid tracking URL link for distributed shell application

[ https://issues.apache.org/jira/browse/YARN-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1157: Attachment: YARN-1157.4.patch ResourceManager UI has invalid tracking URL link for distributed shell

[jira] [Commented] (YARN-49) Improve distributed shell application to work on a secure cluster

[ https://issues.apache.org/jira/browse/YARN-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13775910#comment-13775910 ] Omkar Vinit Joshi commented on YARN-49: --- Thanks vinod.. bq. Because everything else

[jira] [Commented] (YARN-1229) Shell$ExitCodeException could happen if AM fails to start

[ https://issues.apache.org/jira/browse/YARN-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13775918#comment-13775918 ] Bikas Saha commented on YARN-1229: -- We should probably just rename it to MapreduceShuffle.

[jira] [Updated] (YARN-1229) Shell$ExitCodeException could happen if AM fails to start

[ https://issues.apache.org/jira/browse/YARN-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-1229: - Priority: Blocker (was: Critical) Shell$ExitCodeException could happen if AM fails to start

[jira] [Updated] (YARN-1229) Shell$ExitCodeException could happen if AM fails to start

[ https://issues.apache.org/jira/browse/YARN-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-1229: - Hadoop Flags: Incompatible change Shell$ExitCodeException could happen if AM fails to start

[jira] [Commented] (YARN-1089) Add YARN compute units alongside virtual cores

[ https://issues.apache.org/jira/browse/YARN-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13775920#comment-13775920 ] Bikas Saha commented on YARN-1089: -- I am afraid this is getting confusing.

[jira] [Commented] (YARN-1204) Need to add https port related property in Yarn

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

[jira] [Commented] (YARN-1068) Add admin support for HA operations

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

[jira] [Commented] (YARN-49) Improve distributed shell application to work on a secure cluster

[ https://issues.apache.org/jira/browse/YARN-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13775952#comment-13775952 ] Hadoop QA commented on YARN-49: --- {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (YARN-1214) Register ClientToken MasterKey in SecretManager after it is saved

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

[jira] [Commented] (YARN-1157) ResourceManager UI has invalid tracking URL link for distributed shell application

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