[jira] [Commented] (YARN-773) Move YarnRuntimeException from package api.yarn to api.yarn.exceptions

[ https://issues.apache.org/jira/browse/YARN-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677906#comment-13677906 ] Steve Loughran commented on YARN-773: - # Given the grief I had with the last exception r

[jira] [Commented] (YARN-773) Move YarnRuntimeException from package api.yarn to api.yarn.exceptions

[ https://issues.apache.org/jira/browse/YARN-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677908#comment-13677908 ] Steve Loughran commented on YARN-773: - I like new exception classes for testability. If

[jira] [Commented] (YARN-773) Move YarnRuntimeException from package api.yarn to api.yarn.exceptions

[ https://issues.apache.org/jira/browse/YARN-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677917#comment-13677917 ] Steve Loughran commented on YARN-773: - (ignore last comment, wrong JIRA)

[jira] [Commented] (YARN-689) Add multiplier unit to resourcecapabilities

[ https://issues.apache.org/jira/browse/YARN-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677937#comment-13677937 ] Tom White commented on YARN-689: +1 to Hitesh and Bikas' points about minimum (and increment

[jira] [Resolved] (YARN-404) Node Manager leaks Data Node connections

[ https://issues.apache.org/jira/browse/YARN-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj K resolved YARN-404. Resolution: Duplicate > Node Manager leaks Data Node connections > --

[jira] [Updated] (YARN-298) ResourceManager Cluster Applications REST API throws NPE

[ https://issues.apache.org/jira/browse/YARN-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj K updated YARN-298: --- Affects Version/s: 2.0.1-alpha > ResourceManager Cluster Applications REST API throws NPE > ---

[jira] [Resolved] (YARN-781) Expose LOGDIR that containers should use for logging

[ https://issues.apache.org/jira/browse/YARN-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy resolved YARN-781. Resolution: Duplicate Duplicate of YARN-772. > Expose LOGDIR that containers should

[jira] [Commented] (YARN-767) Initialize Application status metrics when QueueMetrics is initialized

[ https://issues.apache.org/jira/browse/YARN-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678013#comment-13678013 ] Arun C Murthy commented on YARN-767: The patch looks good. Nit: initAppStatusMetrics sh

[jira] [Commented] (YARN-648) FS: Add documentation for pluggable policy

[ https://issues.apache.org/jira/browse/YARN-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678096#comment-13678096 ] Karthik Kambatla commented on YARN-648: --- bq. What do you mean by latency? A policy tha

[jira] [Commented] (YARN-760) NodeManager throws AvroRuntimeException on failed start

[ https://issues.apache.org/jira/browse/YARN-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678109#comment-13678109 ] Junping Du commented on YARN-760: - Patch looks good to me. Someone can help to review and co

[jira] [Created] (YARN-783) RM and NM web server /logs pages link not working

Binglin Chang created YARN-783: -- Summary: RM and NM web server /logs pages link not working Key: YARN-783 URL: https://issues.apache.org/jira/browse/YARN-783 Project: Hadoop YARN Issue Type: Bug

[jira] [Created] (YARN-784) YARN does not provide Version info in JMX like hdfs and mapreducev1

Binglin Chang created YARN-784: -- Summary: YARN does not provide Version info in JMX like hdfs and mapreducev1 Key: YARN-784 URL: https://issues.apache.org/jira/browse/YARN-784 Project: Hadoop YARN

[jira] [Commented] (YARN-760) NodeManager throws AvroRuntimeException on failed start

[ https://issues.apache.org/jira/browse/YARN-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678110#comment-13678110 ] Jason Lowe commented on YARN-760: - +1, will commit shortly > NodeManager th

[jira] [Updated] (YARN-784) YARN does not provide Version info in JMX like hdfs and mapreducev1

[ https://issues.apache.org/jira/browse/YARN-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Binglin Chang updated YARN-784: --- Affects Version/s: 2.1.0-beta > YARN does not provide Version info in JMX like hdfs and mapreducev1

[jira] [Commented] (YARN-783) RM and NM web server /logs pages link not working

[ https://issues.apache.org/jira/browse/YARN-783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678112#comment-13678112 ] Binglin Chang commented on YARN-783: The problem seems to only exist in extra jetty cont

[jira] [Commented] (YARN-760) NodeManager throws AvroRuntimeException on failed start

[ https://issues.apache.org/jira/browse/YARN-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678127#comment-13678127 ] Niranjan Singh commented on YARN-760: - Thanks to Jason Lowe, Junping Du and Sandy Ryza f

[jira] [Reopened] (YARN-781) Expose LOGDIR that containers should use for logging

[ https://issues.apache.org/jira/browse/YARN-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reopened YARN-781: -- I read this as more than just documentation. It is about exposing the final LOGDIR a

[jira] [Commented] (YARN-642) Fix up /nodes REST API to have 1 param and be consistent with the Java API

[ https://issues.apache.org/jira/browse/YARN-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678176#comment-13678176 ] Vinod Kumar Vavilapalli commented on YARN-642: -- Looking at it now..

[jira] [Commented] (YARN-775) stream jobs are not cleaning the Yarn local-dirs after container is released

[ https://issues.apache.org/jira/browse/YARN-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678174#comment-13678174 ] yeshavora commented on YARN-775: Setting yarn.nodemanager.delete.debug-delay-sec solves the

[jira] [Resolved] (YARN-775) stream jobs are not cleaning the Yarn local-dirs after container is released

[ https://issues.apache.org/jira/browse/YARN-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yeshavora resolved YARN-775. Resolution: Invalid > stream jobs are not cleaning the Yarn local-dirs after container is released >

[jira] [Updated] (YARN-767) Initialize Application status metrics when QueueMetrics is initialized

[ https://issues.apache.org/jira/browse/YARN-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-767: - Attachment: YARN-767.2.patch Add a test, and fix the visibility of the method > Initialize Applica

[jira] [Commented] (YARN-457) Setting updated nodes from null to null causes NPE in AllocateResponsePBImpl

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

[jira] [Commented] (YARN-553) Have GetNewApplicationResponse generate a directly usable ApplicationSubmissionContext

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

[jira] [Commented] (YARN-602) NodeManager should mandatorily set some Environment variables into every containers that it launches

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

[jira] [Commented] (YARN-641) Make AMLauncher in RM Use NMClient

[ https://issues.apache.org/jira/browse/YARN-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678212#comment-13678212 ] Siddharth Seth commented on YARN-641: - I don't think yarn-client should have a dependenc

[jira] [Created] (YARN-785) Every startContainer request send a set of information (auxiliary service related information) which is redundant. Can be replace with single API.

Omkar Vinit Joshi created YARN-785: -- Summary: Every startContainer request send a set of information (auxiliary service related information) which is redundant. Can be replace with single API. Key: YARN-785 URL:

[jira] [Updated] (YARN-785) Every startContainer request send a set of information (auxiliary service related information) which is redundant. Can be replaced with single NodeManager API.

[ https://issues.apache.org/jira/browse/YARN-785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-785: --- Summary: Every startContainer request send a set of information (auxiliary service related info

[jira] [Commented] (YARN-702) minicluster classpath construction requires user to set yarn.is.minicluster in the job conf

[ https://issues.apache.org/jira/browse/YARN-702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678221#comment-13678221 ] Siddharth Seth commented on YARN-702: - bq. I don't like the idea of the mr client layer

[jira] [Assigned] (YARN-339) TestResourceTrackerService is failing intermittently

[ https://issues.apache.org/jira/browse/YARN-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He reassigned YARN-339: Assignee: Jian He > TestResourceTrackerService is failing intermittently > --

[jira] [Commented] (YARN-752) In AMRMClient, automatically add corresponding rack requests for requested nodes

[ https://issues.apache.org/jira/browse/YARN-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678228#comment-13678228 ] Siddharth Seth commented on YARN-752: - Can we make this rack resolution optional 1) If t

[jira] [Updated] (YARN-777) Remove unreferenced objects from proto

[ https://issues.apache.org/jira/browse/YARN-777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-777: - Attachment: YARN-777.patch After investigation, only found one unused object, yarn_protos.proto.StringURLMapProto

[jira] [Commented] (YARN-649) Make container logs available over HTTP in plain text

[ https://issues.apache.org/jira/browse/YARN-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678238#comment-13678238 ] Sandy Ryza commented on YARN-649: - Somehow messed up the patch's name, but the contents are

[jira] [Commented] (YARN-641) Make AMLauncher in RM Use NMClient

[ https://issues.apache.org/jira/browse/YARN-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678257#comment-13678257 ] Vinod Kumar Vavilapalli commented on YARN-641: -- *sigh* It seems like we'll have

[jira] [Assigned] (YARN-299) Node Manager throws org.apache.hadoop.yarn.state.InvalidStateTransitonException: Invalid event: RESOURCE_FAILED at DONE

[ https://issues.apache.org/jira/browse/YARN-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal reassigned YARN-299: -- Assignee: Mayank Bansal > Node Manager throws > org.apache.hadoop.yarn.state.InvalidStateTra

[jira] [Commented] (YARN-713) ResourceManager can exit unexpectedly if DNS is unavailable

[ https://issues.apache.org/jira/browse/YARN-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678263#comment-13678263 ] Maysam Yabandeh commented on YARN-713: -- Thanks [~tgraves]. The changes of this patch is

[jira] [Commented] (YARN-369) Handle ( or throw a proper error when receiving) status updates from application masters that have not registered

[ https://issues.apache.org/jira/browse/YARN-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678267#comment-13678267 ] Mayank Bansal commented on YARN-369: Hi [~abhishekkapoor], Are you still working on thi

[jira] [Commented] (YARN-752) In AMRMClient, automatically add corresponding rack requests for requested nodes

[ https://issues.apache.org/jira/browse/YARN-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678270#comment-13678270 ] Sandy Ryza commented on YARN-752: - bq. If the user has provided racks - just trust that info

[jira] [Commented] (YARN-752) In AMRMClient, automatically add corresponding rack requests for requested nodes

[ https://issues.apache.org/jira/browse/YARN-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678273#comment-13678273 ] Bikas Saha commented on YARN-752: - YARN's default and most efficient scheduling behavior com

[jira] [Commented] (YARN-752) In AMRMClient, automatically add corresponding rack requests for requested nodes

[ https://issues.apache.org/jira/browse/YARN-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678275#comment-13678275 ] Bikas Saha commented on YARN-752: - The patch looks good to me as is. Need to do a final revi

[jira] [Updated] (YARN-513) Create common proxy client for communicating with RM

[ https://issues.apache.org/jira/browse/YARN-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-513: - Attachment: YARN-513.12.patch rebased on the latest trunk > Create common proxy client for communi

[jira] [Created] (YARN-786) Expose in application resource usage RM REST API

Sandy Ryza created YARN-786: --- Summary: Expose in application resource usage RM REST API Key: YARN-786 URL: https://issues.apache.org/jira/browse/YARN-786 Project: Hadoop YARN Issue Type: Improvemen

[jira] [Updated] (YARN-786) Expose application resource usage in RM REST API

[ https://issues.apache.org/jira/browse/YARN-786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-786: Summary: Expose application resource usage in RM REST API (was: Expose in application resource usage RM REST

[jira] [Commented] (YARN-502) RM crash with NPE on NODE_REMOVED event

[ https://issues.apache.org/jira/browse/YARN-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678300#comment-13678300 ] Mayank Bansal commented on YARN-502: Hi [~sandyr] Are you working on this? Thanks, Ma

[jira] [Commented] (YARN-502) RM crash with NPE on NODE_REMOVED event

[ https://issues.apache.org/jira/browse/YARN-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678306#comment-13678306 ] Sandy Ryza commented on YARN-502: - [~mayank_bansal], I am not. I didn't know how to reproduc

[jira] [Created] (YARN-787) Remove resource min from Yarn client API

Alejandro Abdelnur created YARN-787: --- Summary: Remove resource min from Yarn client API Key: YARN-787 URL: https://issues.apache.org/jira/browse/YARN-787 Project: Hadoop YARN Issue Type: Bu

[jira] [Created] (YARN-788) Rename scheduler resource minimum to increment

Alejandro Abdelnur created YARN-788: --- Summary: Rename scheduler resource minimum to increment Key: YARN-788 URL: https://issues.apache.org/jira/browse/YARN-788 Project: Hadoop YARN Issue Ty

[jira] [Commented] (YARN-777) Remove unreferenced objects from proto

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

[jira] [Created] (YARN-789) Add flag to scheduler to allow zero capabilities in resources

Alejandro Abdelnur created YARN-789: --- Summary: Add flag to scheduler to allow zero capabilities in resources Key: YARN-789 URL: https://issues.apache.org/jira/browse/YARN-789 Project: Hadoop YARN

[jira] [Commented] (YARN-767) Initialize Application status metrics when QueueMetrics is initialized

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

[jira] [Commented] (YARN-713) ResourceManager can exit unexpectedly if DNS is unavailable

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

[jira] [Resolved] (YARN-689) Add multiplier unit to resourcecapabilities

[ https://issues.apache.org/jira/browse/YARN-689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur resolved YARN-689. - Resolution: Won't Fix Closing it and opening other JIRAs to address the discussed changes.

[jira] [Commented] (YARN-513) Create common proxy client for communicating with RM

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

[jira] [Updated] (YARN-787) Remove resource min from Yarn client API

[ https://issues.apache.org/jira/browse/YARN-787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur updated YARN-787: Attachment: YARN-787.patch patch removing the minimum resource from the client API.

[jira] [Comment Edited] (YARN-788) Rename scheduler resource minimum to increment

[ https://issues.apache.org/jira/browse/YARN-788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678378#comment-13678378 ] Alejandro Abdelnur edited comment on YARN-788 at 6/7/13 8:09 PM: -

[jira] [Updated] (YARN-788) Rename scheduler resource minimum to increment

[ https://issues.apache.org/jira/browse/YARN-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur updated YARN-788: Attachment: YARN-788.patch renaming minimum to increment through out the code, and some impro

[jira] [Updated] (YARN-789) Add flag to scheduler to allow zero capabilities in resources

[ https://issues.apache.org/jira/browse/YARN-789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur updated YARN-789: Attachment: YARN-789.patch patch adding boolean configuration that allows zero capabilities i

[jira] [Commented] (YARN-752) In AMRMClient, automatically add corresponding rack requests for requested nodes

[ https://issues.apache.org/jira/browse/YARN-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678401#comment-13678401 ] Alejandro Abdelnur commented on YARN-752: - agree with [~bikassaha]'s, only question

[jira] [Commented] (YARN-752) In AMRMClient, automatically add corresponding rack requests for requested nodes

[ https://issues.apache.org/jira/browse/YARN-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678405#comment-13678405 ] Bikas Saha commented on YARN-752: - User cannot provide a wrong rack for a node. User can pro

[jira] [Commented] (YARN-752) In AMRMClient, automatically add corresponding rack requests for requested nodes

[ https://issues.apache.org/jira/browse/YARN-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678418#comment-13678418 ] Alejandro Abdelnur commented on YARN-752: - Ah!, ok, so before this patch if I would

[jira] [Commented] (YARN-686) Flatten NodeReport

[ https://issues.apache.org/jira/browse/YARN-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678419#comment-13678419 ] Alejandro Abdelnur commented on YARN-686: - +1 > Flatten NodeReport

[jira] [Updated] (YARN-648) FS: Add documentation for pluggable policy

[ https://issues.apache.org/jira/browse/YARN-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-648: -- Attachment: yarn-648-2.patch Patch that addresses Sandy's comments. Thanks Sandy.

[jira] [Commented] (YARN-648) FS: Add documentation for pluggable policy

[ https://issues.apache.org/jira/browse/YARN-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678428#comment-13678428 ] Sandy Ryza commented on YARN-648: - +1, thanks Karthik > FS: Add documentati

[jira] [Commented] (YARN-299) Node Manager throws org.apache.hadoop.yarn.state.InvalidStateTransitonException: Invalid event: RESOURCE_FAILED at DONE

[ https://issues.apache.org/jira/browse/YARN-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678437#comment-13678437 ] Mayank Bansal commented on YARN-299: Looks like there is a race condition here when cont

[jira] [Commented] (YARN-686) Flatten NodeReport

[ https://issues.apache.org/jira/browse/YARN-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678438#comment-13678438 ] Hudson commented on YARN-686: - Integrated in Hadoop-trunk-Commit #3882 (See [https://builds.apa

[jira] [Commented] (YARN-752) In AMRMClient, automatically add corresponding rack requests for requested nodes

[ https://issues.apache.org/jira/browse/YARN-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678445#comment-13678445 ] Siddharth Seth commented on YARN-752: - Alright - I guess the node only request will be h

[jira] [Commented] (YARN-648) FS: Add documentation for pluggable policy

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

[jira] [Commented] (YARN-777) Remove unreferenced objects from proto

[ https://issues.apache.org/jira/browse/YARN-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678448#comment-13678448 ] Zhijie Shen commented on YARN-777: -- +1. Checked the code base, StringURLMapProto is useless

[jira] [Commented] (YARN-752) In AMRMClient, automatically add corresponding rack requests for requested nodes

[ https://issues.apache.org/jira/browse/YARN-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678468#comment-13678468 ] Sandy Ryza commented on YARN-752: - bq. The rack lookup in the patch itself, shouldn't it be

[jira] [Commented] (YARN-752) In AMRMClient, automatically add corresponding rack requests for requested nodes

[ https://issues.apache.org/jira/browse/YARN-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678470#comment-13678470 ] Bikas Saha commented on YARN-752: - The user needs to only specify a node (and may end up get

[jira] [Commented] (YARN-752) In AMRMClient, automatically add corresponding rack requests for requested nodes

[ https://issues.apache.org/jira/browse/YARN-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678472#comment-13678472 ] Bikas Saha commented on YARN-752: - Would be great if the next patch added documentation requ

[jira] [Created] (YARN-790) Use ApplicationSubmissionContext to send tokens instead of file

Bikas Saha created YARN-790: --- Summary: Use ApplicationSubmissionContext to send tokens instead of file Key: YARN-790 URL: https://issues.apache.org/jira/browse/YARN-790 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-767) Initialize Application status metrics when QueueMetrics is initialized

[ https://issues.apache.org/jira/browse/YARN-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-767: - Attachment: YARN-767.3.patch > Initialize Application status metrics when QueueMetrics is initialized > --

[jira] [Created] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

Sandy Ryza created YARN-791: --- Summary: Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API Key: YARN-791 URL: https://issues.apache.org/jira/browse/YARN-791 Project: Hadoop YARN

[jira] [Updated] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

[ https://issues.apache.org/jira/browse/YARN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-791: Issue Type: Sub-task (was: Improvement) Parent: YARN-386 > Ensure that RM RPC APIs that return n

[jira] [Commented] (YARN-642) Fix up /nodes REST API to have 1 param and be consistent with the Java API

[ https://issues.apache.org/jira/browse/YARN-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678521#comment-13678521 ] Sandy Ryza commented on YARN-642: - Thanks for taking a look Vinod. I'll upload a a patch th

[jira] [Created] (YARN-792) Move NodeHealthStatus from yarn.api.record to yarn.server.api.record

Jian He created YARN-792: Summary: Move NodeHealthStatus from yarn.api.record to yarn.server.api.record Key: YARN-792 URL: https://issues.apache.org/jira/browse/YARN-792 Project: Hadoop YARN Issue T

[jira] [Commented] (YARN-686) Flatten NodeReport

[ https://issues.apache.org/jira/browse/YARN-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678528#comment-13678528 ] Jian He commented on YARN-686: -- we should move NodeHealthStatus to yarn.server.api.record after

[jira] [Commented] (YARN-642) Fix up /nodes REST API to have 1 param and be consistent with the Java API

[ https://issues.apache.org/jira/browse/YARN-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678533#comment-13678533 ] Vinod Kumar Vavilapalli commented on YARN-642: -- Not just semantics. Once we sta

[jira] [Updated] (YARN-752) In AMRMClient, automatically add corresponding rack requests for requested nodes

[ https://issues.apache.org/jira/browse/YARN-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-752: Attachment: YARN-752-2.patch > In AMRMClient, automatically add corresponding rack requests for requested

[jira] [Commented] (YARN-752) In AMRMClient, automatically add corresponding rack requests for requested nodes

[ https://issues.apache.org/jira/browse/YARN-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678535#comment-13678535 ] Sandy Ryza commented on YARN-752: - Uploading a patch that modifies the test the catch the is

[jira] [Commented] (YARN-686) Flatten NodeReport

[ https://issues.apache.org/jira/browse/YARN-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678539#comment-13678539 ] Sandy Ryza commented on YARN-686: - Agreed > Flatten NodeReport > --

[jira] [Updated] (YARN-642) Fix up /nodes REST API to have 1 param and be consistent with the Java API

[ https://issues.apache.org/jira/browse/YARN-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-642: Attachment: YARN-642-3.patch > Fix up /nodes REST API to have 1 param and be consistent with the Java API

[jira] [Commented] (YARN-642) Fix up /nodes REST API to have 1 param and be consistent with the Java API

[ https://issues.apache.org/jira/browse/YARN-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678552#comment-13678552 ] Sandy Ryza commented on YARN-642: - OK, that makes sense to me about the APIs. Uploaded a pa

[jira] [Updated] (YARN-792) Move NodeHealthStatus from yarn.api.record to yarn.server.api.record

[ https://issues.apache.org/jira/browse/YARN-792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-792: - Attachment: YARN-792.patch Moved NodeHealthStatus and its PB to yarn.server.api. Moved nodeHealthStatus proto to ya

[jira] [Commented] (YARN-642) Fix up /nodes REST API to have 1 param and be consistent with the Java API

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

[jira] [Commented] (YARN-752) In AMRMClient, automatically add corresponding rack requests for requested nodes

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

[jira] [Updated] (YARN-777) Remove unreferenced objects from proto

[ https://issues.apache.org/jira/browse/YARN-777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-777: - Attachment: YARN-777.1.patch Removed ApplicationStatusProto and ApplicationMasterProto also, thanks for catching t

[jira] [Commented] (YARN-752) In AMRMClient, automatically add corresponding rack requests for requested nodes

[ https://issues.apache.org/jira/browse/YARN-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678561#comment-13678561 ] Vinod Kumar Vavilapalli commented on YARN-752: -- Haven't been paying attention.

[jira] [Updated] (YARN-521) Augment AM - RM client module to be able to request containers only at specific locations

[ https://issues.apache.org/jira/browse/YARN-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-521: - Issue Type: Sub-task (was: Bug) Parent: YARN-386 > Augment AM - RM cli

[jira] [Updated] (YARN-771) AMRMClient support for resource blacklisting

[ https://issues.apache.org/jira/browse/YARN-771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-771: - Issue Type: Sub-task (was: Improvement) Parent: YARN-386 > AMRMClient

[jira] [Updated] (YARN-642) Fix up /nodes REST API to have 1 param and be consistent with the Java API

[ https://issues.apache.org/jira/browse/YARN-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-642: Attachment: YARN-642-4.patch > Fix up /nodes REST API to have 1 param and be consistent with the Java API

[jira] [Commented] (YARN-339) TestResourceTrackerService is failing intermittently

[ https://issues.apache.org/jira/browse/YARN-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678565#comment-13678565 ] Jian He commented on YARN-339: -- set miniClusterMode to be true so that it ignores Metrics sourc

[jira] [Updated] (YARN-339) TestResourceTrackerService is failing intermittently

[ https://issues.apache.org/jira/browse/YARN-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-339: - Attachment: YARN-339.patch > TestResourceTrackerService is failing intermittently > ---

[jira] [Commented] (YARN-777) Remove unreferenced objects from proto

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

[jira] [Commented] (YARN-792) Move NodeHealthStatus from yarn.api.record to yarn.server.api.record

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

[jira] [Commented] (YARN-752) In AMRMClient, automatically add corresponding rack requests for requested nodes

[ https://issues.apache.org/jira/browse/YARN-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678578#comment-13678578 ] Alejandro Abdelnur commented on YARN-752: - bq. I think if the user gives a wrong rac

[jira] [Commented] (YARN-339) TestResourceTrackerService is failing intermittently

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

[jira] [Commented] (YARN-642) Fix up /nodes REST API to have 1 param and be consistent with the Java API

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

[jira] [Commented] (YARN-752) In AMRMClient, automatically add corresponding rack requests for requested nodes

[ https://issues.apache.org/jira/browse/YARN-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678613#comment-13678613 ] Sandy Ryza commented on YARN-752: - In my vision of YARN-521, we will add an additional boole

[jira] [Commented] (YARN-777) Remove unreferenced objects from proto

[ https://issues.apache.org/jira/browse/YARN-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678622#comment-13678622 ] Hudson commented on YARN-777: - Integrated in Hadoop-trunk-Commit #3884 (See [https://builds.apa

  1   2   >