[jira] [Commented] (YARN-380) yarn node -status prints Last-Last-Node-Status

[ https://issues.apache.org/jira/browse/YARN-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586845#comment-13586845 ] Abhishek Kapoor commented on YARN-380: -- Also I am proposing to use DateFormat.LONG whic

[jira] [Commented] (YARN-380) yarn node -status prints Last-Last-Node-Status

[ https://issues.apache.org/jira/browse/YARN-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586843#comment-13586843 ] Abhishek Kapoor commented on YARN-380: -- I guess Thomas you mean instead of "Last-Last-H

[jira] [Assigned] (YARN-380) yarn node -status prints Last-Last-Node-Status

[ https://issues.apache.org/jira/browse/YARN-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kapoor reassigned YARN-380: Assignee: Abhishek Kapoor > yarn node -status prints Last-Last-Node-Status >

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

[jira] [Resolved] (YARN-310) RM changes to handle NM heartbeat during overload

[ https://issues.apache.org/jira/browse/YARN-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong resolved YARN-310. Resolution: Duplicate > RM changes to handle NM heartbeat during overload > -

[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=13586702#comment-13586702 ] Sandy Ryza commented on YARN-417: - Thanks for the comments Bikas, and for your perspective,

[jira] [Commented] (YARN-365) Each NM heartbeat should not generate an event for the Scheduler

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

[jira] [Commented] (YARN-365) Each NM heartbeat should not generate an event for the Scheduler

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

[jira] [Commented] (YARN-365) Each NM heartbeat should not generate an event for the Scheduler

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

[jira] [Commented] (YARN-365) Each NM heartbeat should not generate an event for the Scheduler

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

[jira] [Commented] (YARN-398) Allow white-list and black-list of resources

[ https://issues.apache.org/jira/browse/YARN-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586615#comment-13586615 ] Alejandro Abdelnur commented on YARN-398: - Arun, how is this different from option #

[jira] [Updated] (YARN-365) Each NM heartbeat should not generate an event for the Scheduler

[ https://issues.apache.org/jira/browse/YARN-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated YARN-365: Attachment: YARN-365.10.patch Updated with the renamed method, and some javadoc. Will commit post jen

[jira] [Commented] (YARN-365) Each NM heartbeat should not generate an event for the Scheduler

[ https://issues.apache.org/jira/browse/YARN-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586603#comment-13586603 ] Siddharth Seth commented on YARN-365: - One minor refactor, for which I'm uploading a pat

[jira] [Commented] (YARN-365) Each NM heartbeat should not generate an event for the Scheduler

[ https://issues.apache.org/jira/browse/YARN-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586601#comment-13586601 ] Siddharth Seth commented on YARN-365: - +1. Committing this, and ignoring the jenkins -1

[jira] [Commented] (YARN-392) Make it possible to schedule to specific nodes without dropping locality

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586579#comment-13586579 ] Arun C Murthy commented on YARN-392: Take a look at YARN-398 for a simpler alternate pro

[jira] [Commented] (YARN-398) Allow white-list and black-list of resources

[ https://issues.apache.org/jira/browse/YARN-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586576#comment-13586576 ] Arun C Murthy commented on YARN-398: Here is an approach I have a prelim patch on which

[jira] [Commented] (YARN-365) Each NM heartbeat should not generate an event for the Scheduler

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

[jira] [Commented] (YARN-424) Allow resource requests to provide hints to the scheduler

[ https://issues.apache.org/jira/browse/YARN-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586560#comment-13586560 ] Bikas Saha commented on YARN-424: - I agree that being able to extend the API without breakin

[jira] [Commented] (YARN-392) Make it possible to schedule to specific nodes without dropping locality

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586544#comment-13586544 ] Arun C Murthy commented on YARN-392: Also, we don't have to support *all* features in th

[jira] [Commented] (YARN-424) Allow resource requests to provide hints to the scheduler

[ https://issues.apache.org/jira/browse/YARN-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586535#comment-13586535 ] Arun C Murthy commented on YARN-424: Also, the reason we have invested in using protobuf

[jira] [Commented] (YARN-392) Make it possible to schedule to specific nodes without dropping locality

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586529#comment-13586529 ] Arun C Murthy commented on YARN-392: Gang-scheduling, deadline-scheduling etc. are not *

[jira] [Commented] (YARN-424) Allow resource requests to provide hints to the scheduler

[ https://issues.apache.org/jira/browse/YARN-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586526#comment-13586526 ] Arun C Murthy commented on YARN-424: I'm not a fan of stringly-typed 'features' in the S

[jira] [Commented] (YARN-390) ApplicationCLI and NodeCLI use hard-coded platform-specific line separator, which causes test failures on Windows

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

[jira] [Commented] (YARN-390) ApplicationCLI and NodeCLI use hard-coded platform-specific line separator, which causes test failures on Windows

[ https://issues.apache.org/jira/browse/YARN-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586513#comment-13586513 ] Suresh Srinivas commented on YARN-390: -- +1 for the patch. I will commit this shortly.

[jira] [Updated] (YARN-365) Each NM heartbeat should not generate an event for the Scheduler

[ https://issues.apache.org/jira/browse/YARN-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-365: --- Attachment: YARN-365.9.patch > Each NM heartbeat should not generate an event for the Scheduler > -

[jira] [Commented] (YARN-365) Each NM heartbeat should not generate an event for the Scheduler

[ https://issues.apache.org/jira/browse/YARN-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586278#comment-13586278 ] Siddharth Seth commented on YARN-365: - Almost there. Couple more fixes needed though. -

[jira] [Created] (YARN-426) Failure to download a public resource on a node prevents further downloads of the resource from that node

Jason Lowe created YARN-426: --- Summary: Failure to download a public resource on a node prevents further downloads of the resource from that node Key: YARN-426 URL: https://issues.apache.org/jira/browse/YARN-426

[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=13586127#comment-13586127 ] 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 ] Chris Riccomini updated YARN-417: - Attachment: YarnAppMasterListener.java YarnAppMaster.java Hey Guys, I'm attaching

[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=13586092#comment-13586092 ] Bikas Saha commented on YARN-417: - My first comment would be to see if we can provide this f

[jira] [Updated] (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:all-tabpanel ] Abhishek Kapoor updated YARN-379: - Attachment: YARN-379.patch Please review the code. Many Thanks > yarn [node,appli

[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-tabpanel&focusedCommentId=13586086#comment-13586086 ] Abhishek Kapoor commented on YARN-379: -- Do I need any special permission to attach a pa

[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=13586070#comment-13586070 ] Sandy Ryza commented on YARN-417: - Sorry, good point. The patch is a work in progress and 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=13586051#comment-13586051 ] Bikas Saha commented on YARN-417: - Sandy, it will be beneficial if you can mention if the pa

[jira] [Commented] (YARN-421) Create asynchronous AM RM Client

[ https://issues.apache.org/jira/browse/YARN-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586033#comment-13586033 ] Chris Riccomini commented on YARN-421: -- Seems like it might be. I'm going to comment on

[jira] [Updated] (YARN-420) Enable the RM to work with AM's that are not managed by it

[ https://issues.apache.org/jira/browse/YARN-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated YARN-420: --- Labels: incom mrv2 (was: mrv2) > Enable the RM to work with AM's that are not managed by it >

[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-tabpanel&focusedCommentId=13586002#comment-13586002 ] Abhishek Kapoor commented on YARN-379: -- It order to fix this request, two files will be

[jira] [Commented] (YARN-345) Many InvalidStateTransitonException errors for ApplicationImpl in Node Manager

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

[jira] [Updated] (YARN-345) Many InvalidStateTransitonException errors for ApplicationImpl in Node Manager

[ https://issues.apache.org/jira/browse/YARN-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated YARN-345: --- Attachment: YARN-345.patch > Many InvalidStateTransitonException errors for ApplicationImpl in Node

[jira] [Commented] (YARN-424) Allow resource requests to provide hints to the scheduler

[ https://issues.apache.org/jira/browse/YARN-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13585965#comment-13585965 ] Alejandro Abdelnur commented on YARN-424: - Regarding the format/type for hints, whil

[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-tabpanel&focusedCommentId=13585949#comment-13585949 ] Thomas Graves commented on YARN-379: I added you as a contributor to the YARN project an

[jira] [Updated] (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:all-tabpanel ] Thomas Graves updated YARN-379: --- Assignee: Abhishek Kapoor > yarn [node,application] command print logger info messages > --

[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-tabpanel&focusedCommentId=13585938#comment-13585938 ] Abhishek Kapoor commented on YARN-379: -- I would like to fix it, could someone help me o

[jira] [Commented] (YARN-425) coverage fix for yarn api

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

[jira] [Updated] (YARN-425) coverage fix for yarn api

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

[jira] [Updated] (YARN-425) coverage fix for yarn api

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

[jira] [Created] (YARN-425) coverage fix for yarn api

Aleksey Gorshkov created YARN-425: - Summary: coverage fix for yarn api Key: YARN-425 URL: https://issues.apache.org/jira/browse/YARN-425 Project: Hadoop YARN Issue Type: Test Affects Vers

[jira] [Resolved] (YARN-111) Application level priority in Resource Manager Schedulers

[ https://issues.apache.org/jira/browse/YARN-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nemon lou resolved YARN-111. Resolution: Won't Fix > Application level priority in Resource Manager Schedulers > -

[jira] [Commented] (YARN-392) Make it possible to schedule to specific nodes without dropping locality

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13585744#comment-13585744 ] Sandy Ryza commented on YARN-392: - Filed YARN-424 for Alejandro's hints proposal.

[jira] [Created] (YARN-424) Allow resource requests to provide hints to the scheduler

Sandy Ryza created YARN-424: --- Summary: Allow resource requests to provide hints to the scheduler Key: YARN-424 URL: https://issues.apache.org/jira/browse/YARN-424 Project: Hadoop YARN Issue Type:

[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: Issue Type: Sub-task (was: New Feature) Parent: YARN-418 > Add a poller that allows the AM to re

[jira] [Commented] (YARN-421) Create asynchronous AM RM Client

[ https://issues.apache.org/jira/browse/YARN-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13585725#comment-13585725 ] Sandy Ryza commented on YARN-421: - Is this a duplicate of YARN-417? > Creat