[jira] [Commented] (YARN-1044) used/min/max resources do not display info in the scheduler page

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

[jira] [Updated] (YARN-1044) used/min/max resources do not display info in the scheduler page

[ https://issues.apache.org/jira/browse/YARN-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-1044: -- Attachment: yarn-1044.patch > used/min/max resources do not display info in the scheduler page > ---

[jira] [Updated] (YARN-1044) used/min/max resources do not display info in the scheduler page

[ https://issues.apache.org/jira/browse/YARN-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-1044: -- Attachment: (was: yarn-1044.patch) > used/min/max resources do not display info in the scheduler

[jira] [Commented] (YARN-1044) used/min/max resources do not display info in the scheduler page

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

[jira] [Updated] (YARN-1044) used/min/max resources do not display info in the scheduler page

[ https://issues.apache.org/jira/browse/YARN-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-1044: -- Attachment: yarn-1044.patch > used/min/max resources do not display info in the scheduler page > ---

[jira] [Updated] (YARN-1044) used/min/max resources do not display info in the scheduler page

[ https://issues.apache.org/jira/browse/YARN-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-1044: -- Attachment: (was: yarn-1044.patch) > used/min/max resources do not display info in the scheduler

[jira] [Commented] (YARN-1004) yarn.scheduler.minimum|maximum|increment-allocation-mb should be prefixed with the scheduler type

[ https://issues.apache.org/jira/browse/YARN-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740735#comment-13740735 ] Bikas Saha commented on YARN-1004: -- IMO the intent of yarn.scheduler.max is to be an admin

[jira] [Commented] (YARN-1048) Add new AMRMClientAsync.getMatchingRequests method taking a Container as parameter

[ https://issues.apache.org/jira/browse/YARN-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740731#comment-13740731 ] Hitesh Shah commented on YARN-1048: --- [~josephkniest] That would be org.apache.hadoop.yarn

[jira] [Commented] (YARN-1048) Add new AMRMClientAsync.getMatchingRequests method taking a Container as parameter

[ https://issues.apache.org/jira/browse/YARN-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740729#comment-13740729 ] Joseph Kniest commented on YARN-1048: - Hi, new to hadoop. In beginning to solve this I'

[jira] [Commented] (YARN-1006) Nodes list web page on the RM web UI is broken

[ https://issues.apache.org/jira/browse/YARN-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740694#comment-13740694 ] Hitesh Shah commented on YARN-1006: --- [~vinodkv] [~xgong] Is this a blocker for 2.1.0?

[jira] [Commented] (YARN-1006) Nodes list web page on the RM web UI is broken

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

[jira] [Commented] (YARN-1006) Nodes list web page on the RM web UI is broken

[ https://issues.apache.org/jira/browse/YARN-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740673#comment-13740673 ] Xuan Gong commented on YARN-1006: - Trivial patch. No tests added > Nodes l

[jira] [Updated] (YARN-1006) Nodes list web page on the RM web UI is broken

[ https://issues.apache.org/jira/browse/YARN-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1006: Attachment: YARN-1006.1.patch The reason why the page is not showing in correct format/style is because at

[jira] [Updated] (YARN-1004) yarn.scheduler.minimum|maximum|increment-allocation-mb should be prefixed with the scheduler type

[ https://issues.apache.org/jira/browse/YARN-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur updated YARN-1004: - Fix Version/s: 2.1.0-beta setting the fix version to 2.1.0-beta so we don't missed before

[jira] [Commented] (YARN-1064) YarnConfiguration scheduler configuration constants are not consistent

[ https://issues.apache.org/jira/browse/YARN-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740657#comment-13740657 ] Alejandro Abdelnur commented on YARN-1064: -- The ones that caught my eye are: {cod

[jira] [Commented] (YARN-1055) Handle app recovery differently for AM failures and RM restart

[ https://issues.apache.org/jira/browse/YARN-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740650#comment-13740650 ] Alejandro Abdelnur commented on YARN-1055: -- [~bikassaha], [~vinodkv], in Hadoop 1

[jira] [Commented] (YARN-1056) Fix configs yarn.resourcemanager.resourcemanager.connect.{max.wait.secs|retry_interval.secs}

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

[jira] [Updated] (YARN-1056) Fix configs yarn.resourcemanager.resourcemanager.connect.{max.wait.secs|retry_interval.secs}

[ https://issues.apache.org/jira/browse/YARN-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1056: Priority: Trivial (was: Blocker) > Fix configs > yarn.resourcemanager.resourcemanager.connect.

[jira] [Commented] (YARN-1064) YarnConfiguration scheduler configuration constants are not consistent

[ https://issues.apache.org/jira/browse/YARN-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740601#comment-13740601 ] Vinod Kumar Vavilapalli commented on YARN-1064: --- Can you list the specific ch

[jira] [Commented] (YARN-1004) yarn.scheduler.minimum|maximum|increment-allocation-mb should be prefixed with the scheduler type

[ https://issues.apache.org/jira/browse/YARN-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740597#comment-13740597 ] Vinod Kumar Vavilapalli commented on YARN-1004: --- Like I mentioned, Fifo and C

[jira] [Commented] (YARN-1055) Handle app recovery differently for AM failures and RM restart

[ https://issues.apache.org/jira/browse/YARN-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740576#comment-13740576 ] Vinod Kumar Vavilapalli commented on YARN-1055: --- Same here :) We do really un

[jira] [Commented] (YARN-1055) Handle app recovery differently for AM failures and RM restart

[ https://issues.apache.org/jira/browse/YARN-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740500#comment-13740500 ] Bikas Saha commented on YARN-1055: -- Thats exactly what I was trying to say earlier. That R

[jira] [Commented] (YARN-1055) Handle app recovery differently for AM failures and RM restart

[ https://issues.apache.org/jira/browse/YARN-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740495#comment-13740495 ] Karthik Kambatla commented on YARN-1055: Thinking more about it, the issue is not l

[jira] [Commented] (YARN-1055) Handle app recovery differently for AM failures and RM restart

[ https://issues.apache.org/jira/browse/YARN-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740474#comment-13740474 ] Bikas Saha commented on YARN-1055: -- Why does the launcher not retry the action? Is there a

[jira] [Commented] (YARN-1055) Handle app recovery differently for AM failures and RM restart

[ https://issues.apache.org/jira/browse/YARN-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740446#comment-13740446 ] Robert Kanter commented on YARN-1055: - Another way of phrasing this: when the action's

[jira] [Commented] (YARN-1055) Handle app recovery differently for AM failures and RM restart

[ https://issues.apache.org/jira/browse/YARN-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740436#comment-13740436 ] Karthik Kambatla commented on YARN-1055: This problem doesn't exist in Hadoop-1 bec

[jira] [Commented] (YARN-1044) used/min/max resources do not display info in the scheduler page

[ https://issues.apache.org/jira/browse/YARN-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740437#comment-13740437 ] Sangjin Lee commented on YARN-1044: --- By the way, the xml issue with the capacity schedule

[jira] [Commented] (YARN-1044) used/min/max resources do not display info in the scheduler page

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

[jira] [Commented] (YARN-1055) Handle app recovery differently for AM failures and RM restart

[ https://issues.apache.org/jira/browse/YARN-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740435#comment-13740435 ] Karthik Kambatla commented on YARN-1055: In Hadoop 1, we set the job.recovery.enabl

[jira] [Updated] (YARN-1044) used/min/max resources do not display info in the scheduler page

[ https://issues.apache.org/jira/browse/YARN-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-1044: -- Attachment: yarn-1044.patch Proposed patch for escaping invalid characters for html. >

[jira] [Commented] (YARN-1055) Handle app recovery differently for AM failures and RM restart

[ https://issues.apache.org/jira/browse/YARN-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740367#comment-13740367 ] Bikas Saha commented on YARN-1055: -- How does it work in hadoop 1 then? From what I see the

[jira] [Commented] (YARN-1055) Handle app recovery differently for AM failures and RM restart

[ https://issues.apache.org/jira/browse/YARN-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740362#comment-13740362 ] Karthik Kambatla commented on YARN-1055: As in my comment from above (https://issu

[jira] [Updated] (YARN-1065) NM should provide AuxillaryService data to the container

[ https://issues.apache.org/jira/browse/YARN-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-1065: -- Target Version/s: 2.1.1-beta > NM should provide AuxillaryService data to the container > --

[jira] [Updated] (YARN-1065) NM should provide AuxillaryService data to the container

[ https://issues.apache.org/jira/browse/YARN-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-1065: -- Affects Version/s: (was: 2.0.4-alpha) > NM should provide AuxillaryService data to the container

[jira] [Updated] (YARN-1065) NM should provide AuxillaryService data to the container

[ https://issues.apache.org/jira/browse/YARN-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-1065: -- Affects Version/s: (was: 2.1.1-beta) 2.0.4-alpha > NM should provide Auxi

[jira] [Created] (YARN-1065) NM should provide AuxillaryService data to the container

Bikas Saha created YARN-1065: Summary: NM should provide AuxillaryService data to the container Key: YARN-1065 URL: https://issues.apache.org/jira/browse/YARN-1065 Project: Hadoop YARN Issue Type

[jira] [Commented] (YARN-1049) ContainerExistStatus and ContainerState are defined incorrectly

[ https://issues.apache.org/jira/browse/YARN-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740265#comment-13740265 ] Zhijie Shen commented on YARN-1049: --- bq. ContainerExitStatus defines a few constant with

[jira] [Commented] (YARN-305) Too many 'Node offerred to app:..." messages in RM

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

[jira] [Commented] (YARN-1055) Handle app recovery differently for AM failures and RM restart

[ https://issues.apache.org/jira/browse/YARN-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740249#comment-13740249 ] Alejandro Abdelnur commented on YARN-1055: -- [~rkanter], [~kkambatl], can you pleas

[jira] [Commented] (YARN-1055) Handle app recovery differently for AM failures and RM restart

[ https://issues.apache.org/jira/browse/YARN-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740242#comment-13740242 ] Bikas Saha commented on YARN-1055: -- First of all, whatever needs to be set must be set in

[jira] [Commented] (YARN-1064) YarnConfiguration scheduler configuration constants are not consistent

[ https://issues.apache.org/jira/browse/YARN-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740239#comment-13740239 ] Zhijie Shen commented on YARN-1064: --- It sounds good to uniform the prefix. Better to use

[jira] [Commented] (YARN-1008) MiniYARNCluster with multiple nodemanagers, all nodes have same key for allocations

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

[jira] [Updated] (YARN-305) Too many 'Node offerred to app:..." messages in RM

[ https://issues.apache.org/jira/browse/YARN-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lohit Vijayarenu updated YARN-305: -- Attachment: YARN-305.1.patch Had generated diff from old branch. Reattaching diff.

[jira] [Updated] (YARN-305) Too many 'Node offerred to app:..." messages in RM

[ https://issues.apache.org/jira/browse/YARN-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lohit Vijayarenu updated YARN-305: -- Attachment: (was: YARN-305.1.patch) > Too many 'Node offerred to app:..." messages in RM

[jira] [Commented] (YARN-1064) YarnConfiguration scheduler configuration constants are not consistent

[ https://issues.apache.org/jira/browse/YARN-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740216#comment-13740216 ] Sandy Ryza commented on YARN-1064: -- I think this is only for the scheduler configs. Do yo

[jira] [Commented] (YARN-1008) MiniYARNCluster with multiple nodemanagers, all nodes have same key for allocations

[ https://issues.apache.org/jira/browse/YARN-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740211#comment-13740211 ] Omkar Vinit Joshi commented on YARN-1008: - +1.. lgtm > MiniYARNClu

[jira] [Commented] (YARN-1064) YarnConfiguration scheduler configuration constants are not consistent

[ https://issues.apache.org/jira/browse/YARN-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740207#comment-13740207 ] Omkar Vinit Joshi commented on YARN-1064: - like..RM_PREFIX..clearly means it is for

[jira] [Updated] (YARN-1064) YarnConfiguration scheduler configuration constants are not consistent

[ https://issues.apache.org/jira/browse/YARN-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-1064: Labels: newbie (was: ) > YarnConfiguration scheduler configuration constants are not co

[jira] [Commented] (YARN-1055) Handle app recovery differently for AM failures and RM restart

[ https://issues.apache.org/jira/browse/YARN-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740204#comment-13740204 ] Alejandro Abdelnur commented on YARN-1055: -- [~bikassaha], bq. Restart on am fail

[jira] [Commented] (YARN-305) Too many 'Node offerred to app:..." messages in RM

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

[jira] [Commented] (YARN-1008) MiniYARNCluster with multiple nodemanagers, all nodes have same key for allocations

[ https://issues.apache.org/jira/browse/YARN-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740198#comment-13740198 ] Sandy Ryza commented on YARN-1008: -- +1 > MiniYARNCluster with multiple no

[jira] [Updated] (YARN-305) Too many 'Node offerred to app:..." messages in RM

[ https://issues.apache.org/jira/browse/YARN-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lohit Vijayarenu updated YARN-305: -- Attachment: YARN-305.1.patch Simple patch to change log level to debug and add node information.

[jira] [Updated] (YARN-1008) MiniYARNCluster with multiple nodemanagers, all nodes have same key for allocations

[ https://issues.apache.org/jira/browse/YARN-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur updated YARN-1008: - Attachment: YARN-1008.patch missed the dot before node, fixed. also added javadocs to the

[jira] [Commented] (YARN-1064) YarnConfiguration scheduler configuration constants are not consistent

[ https://issues.apache.org/jira/browse/YARN-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740178#comment-13740178 ] Alejandro Abdelnur commented on YARN-1064: -- [~ojoshi], can you please explain why

[jira] [Commented] (YARN-1063) Winutils needs ability to create task as domain user

[ https://issues.apache.org/jira/browse/YARN-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740167#comment-13740167 ] Bikas Saha commented on YARN-1063: -- Can you please provide some overall design approach. P

[jira] [Commented] (YARN-1055) Handle app recovery differently for AM failures and RM restart

[ https://issues.apache.org/jira/browse/YARN-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740162#comment-13740162 ] Karthik Kambatla commented on YARN-1055: [~hitesh], you are right - we should be ca

[jira] [Commented] (YARN-1064) YarnConfiguration scheduler configuration constants are not consistent

[ https://issues.apache.org/jira/browse/YARN-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740161#comment-13740161 ] Omkar Vinit Joshi commented on YARN-1064: - I think this is more intuitive the way i

[jira] [Commented] (YARN-1008) MiniYARNCluster with multiple nodemanagers, all nodes have same key for allocations

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

[jira] [Commented] (YARN-1008) MiniYARNCluster with multiple nodemanagers, all nodes have same key for allocations

[ https://issues.apache.org/jira/browse/YARN-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740101#comment-13740101 ] Sandy Ryza commented on YARN-1008: -- Is there a reason for using "include-port-in-node.name

[jira] [Updated] (YARN-1008) MiniYARNCluster with multiple nodemanagers, all nodes have same key for allocations

[ https://issues.apache.org/jira/browse/YARN-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur updated YARN-1008: - Attachment: YARN-1008.patch Addressed all comments. Created YARN-1064 as there are some s

[jira] [Created] (YARN-1064) YarnConfiguration scheduler configuration constants are not consistent

Alejandro Abdelnur created YARN-1064: Summary: YarnConfiguration scheduler configuration constants are not consistent Key: YARN-1064 URL: https://issues.apache.org/jira/browse/YARN-1064 Project: H

[jira] [Updated] (YARN-1004) yarn.scheduler.minimum|maximum|increment-allocation-mb should be prefixed with the scheduler type

[ https://issues.apache.org/jira/browse/YARN-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur updated YARN-1004: - Summary: yarn.scheduler.minimum|maximum|increment-allocation-mb should be prefixed with th

[jira] [Updated] (YARN-1063) Winutils needs ability to create task as domain user

[ https://issues.apache.org/jira/browse/YARN-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kyle Leckie updated YARN-1063: -- Attachment: (was: YARN-732.patch) > Winutils needs ability to create task as domain user > -

[jira] [Updated] (YARN-1063) Winutils needs ability to create task as domain user

[ https://issues.apache.org/jira/browse/YARN-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kyle Leckie updated YARN-1063: -- Attachment: YARN-732.patch code patch > Winutils needs ability to create task as domain

[jira] [Commented] (YARN-867) Isolation of failures in aux services

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

[jira] [Updated] (YARN-1063) Winutils needs ability to create task as domain user

[ https://issues.apache.org/jira/browse/YARN-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kyle Leckie updated YARN-1063: -- Attachment: YARN-732.patch Code patch > Winutils needs ability to create task as domain

[jira] [Commented] (YARN-1061) NodeManager is indefinitely waiting for nodeHeartBeat() response from ResouceManager.

[ https://issues.apache.org/jira/browse/YARN-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740048#comment-13740048 ] Omkar Vinit Joshi commented on YARN-1061: - How can NM wait infinitely? I mean what

[jira] [Commented] (YARN-867) Isolation of failures in aux services

[ https://issues.apache.org/jira/browse/YARN-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740042#comment-13740042 ] Hitesh Shah commented on YARN-867: -- Might be good to break this down in a subset of jiras.

[jira] [Assigned] (YARN-1006) Nodes list web page on the RM web UI is broken

[ https://issues.apache.org/jira/browse/YARN-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong reassigned YARN-1006: --- Assignee: Xuan Gong (was: Jian He) > Nodes list web page on the RM web UI is broken > ---

[jira] [Updated] (YARN-867) Isolation of failures in aux services

[ https://issues.apache.org/jira/browse/YARN-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-867: --- Attachment: YARN-867.1.sampleCode.patch > Isolation of failures in aux services >

[jira] [Commented] (YARN-867) Isolation of failures in aux services

[ https://issues.apache.org/jira/browse/YARN-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740009#comment-13740009 ] Xuan Gong commented on YARN-867: My proposal: When there is any auxService failure, instead

[jira] [Commented] (YARN-1059) '\n' or ' ' or '\t' should be ignored for some configuration parameters

[ https://issues.apache.org/jira/browse/YARN-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740005#comment-13740005 ] Zhijie Shen commented on YARN-1059: --- it's duplicate with HADOOP-9869 > '

[jira] [Updated] (YARN-1059) '\n' or ' ' or '\t' should be ignored for some configuration parameters

[ https://issues.apache.org/jira/browse/YARN-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-1059: Summary: '\n' or ' ' or '\t' should be ignored for some configuration parameters (was: Ille

[jira] [Commented] (YARN-1059) IllegalArgumentException while starting YARN

[ https://issues.apache.org/jira/browse/YARN-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1373#comment-1373 ] Omkar Vinit Joshi commented on YARN-1059: - Modifying title > Illeg

[jira] [Commented] (YARN-1059) IllegalArgumentException while starting YARN

[ https://issues.apache.org/jira/browse/YARN-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739997#comment-13739997 ] Omkar Vinit Joshi commented on YARN-1059: - Today none of the configuration paramete

[jira] [Updated] (YARN-1059) IllegalArgumentException while starting YARN

[ https://issues.apache.org/jira/browse/YARN-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-1059: Labels: newbie (was: ) > IllegalArgumentException while starting YARN > ---

[jira] [Updated] (YARN-1059) IllegalArgumentException while starting YARN

[ https://issues.apache.org/jira/browse/YARN-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-1059: Priority: Minor (was: Major) > IllegalArgumentException while starting YARN > -

[jira] [Created] (YARN-1063) Winutils needs ability to create task as domain user

Kyle Leckie created YARN-1063: - Summary: Winutils needs ability to create task as domain user Key: YARN-1063 URL: https://issues.apache.org/jira/browse/YARN-1063 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-292) ResourceManager throws ArrayIndexOutOfBoundsException while handling CONTAINER_ALLOCATED for application attempt

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

[jira] [Commented] (YARN-1008) MiniYARNCluster with multiple nodemanagers, all nodes have same key for allocations

[ https://issues.apache.org/jira/browse/YARN-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739913#comment-13739913 ] Sandy Ryza commented on YARN-1008: -- A few comments: Can we call the config RM_SCHEDULER_I

[jira] [Commented] (YARN-1024) Define a virtual core unambigiously

[ https://issues.apache.org/jira/browse/YARN-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739900#comment-13739900 ] Sandy Ryza commented on YARN-1024: -- bq. I would also like us to have a flag that would eit

[jira] [Updated] (YARN-292) ResourceManager throws ArrayIndexOutOfBoundsException while handling CONTAINER_ALLOCATED for application attempt

[ https://issues.apache.org/jira/browse/YARN-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-292: - Attachment: YARN-292.2.patch Updated the patch to add comments and assert in AMContainerAllocatedTransition

[jira] [Commented] (YARN-1024) Define a virtual core unambigiously

[ https://issues.apache.org/jira/browse/YARN-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739853#comment-13739853 ] Robert Joseph Evans commented on YARN-1024: --- {quote}Sorry for the longwindedness.

[jira] [Commented] (YARN-1055) Handle app recovery differently for AM failures and RM restart

[ https://issues.apache.org/jira/browse/YARN-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739829#comment-13739829 ] Hitesh Shah commented on YARN-1055: --- [~kkambatl] Based on the discussion, I was trying to

[jira] [Commented] (YARN-1044) used/min/max resources do not display info in the scheduler page

[ https://issues.apache.org/jira/browse/YARN-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739802#comment-13739802 ] Sangjin Lee commented on YARN-1044: --- Sounds good. I'll submit a patch soon.

[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-tabpanel&focusedCommentId=13739801#comment-13739801 ] Sangjin Lee commented on YARN-451: -- I agree that hadoop 1 was different as the notion of ma

[jira] [Commented] (YARN-1060) Two tests in TestFairScheduler are missing @Test annotation

[ https://issues.apache.org/jira/browse/YARN-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739711#comment-13739711 ] Hudson commented on YARN-1060: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1518 (See [htt

[jira] [Commented] (YARN-337) RM handles killed application tracking URL poorly

[ https://issues.apache.org/jira/browse/YARN-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739713#comment-13739713 ] Hudson commented on YARN-337: - SUCCESS: Integrated in Hadoop-trunk-Commit #4257 (See [https://b

[jira] [Commented] (YARN-1060) Two tests in TestFairScheduler are missing @Test annotation

[ https://issues.apache.org/jira/browse/YARN-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739656#comment-13739656 ] Hudson commented on YARN-1060: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1491 (See [https://

[jira] [Commented] (YARN-1023) [YARN-321] Webservices REST API's support for Application History

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

[jira] [Commented] (YARN-954) [YARN-321] History Service should create the webUI and wire it to HistoryStorage

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

[jira] [Updated] (YARN-954) [YARN-321] History Service should create the webUI and wire it to HistoryStorage

[ https://issues.apache.org/jira/browse/YARN-954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj K updated YARN-954: --- Attachment: YARN-954-v2.patch > [YARN-321] History Service should create the webUI and wire it to > Histor

[jira] [Updated] (YARN-1023) [YARN-321] Webservices REST API's support for Application History

[ https://issues.apache.org/jira/browse/YARN-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj K updated YARN-1023: Attachment: YARN-1023-v1.patch > [YARN-321] Webservices REST API's support for Application History > ---

[jira] [Commented] (YARN-1036) Distributed Cache gives inconsistent result if cache files get deleted from task tracker

[ https://issues.apache.org/jira/browse/YARN-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739540#comment-13739540 ] Hudson commented on YARN-1036: -- FAILURE: Integrated in Hadoop-Hdfs-0.23-Build #699 (See [http

[jira] [Commented] (YARN-543) [Umbrella] NodeManager localization related issues

[ https://issues.apache.org/jira/browse/YARN-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739541#comment-13739541 ] Hudson commented on YARN-543: - FAILURE: Integrated in Hadoop-Hdfs-0.23-Build #699 (See [https:/

[jira] [Commented] (YARN-1060) Two tests in TestFairScheduler are missing @Test annotation

[ https://issues.apache.org/jira/browse/YARN-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739521#comment-13739521 ] Hudson commented on YARN-1060: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #301 (See [https://b

[jira] [Commented] (YARN-292) ResourceManager throws ArrayIndexOutOfBoundsException while handling CONTAINER_ALLOCATED for application attempt

[ https://issues.apache.org/jira/browse/YARN-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739424#comment-13739424 ] Junping Du commented on YARN-292: - bq. I'll document it as the comment in AMContainerAllocat

[jira] [Commented] (YARN-292) ResourceManager throws ArrayIndexOutOfBoundsException while handling CONTAINER_ALLOCATED for application attempt

[ https://issues.apache.org/jira/browse/YARN-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739378#comment-13739378 ] Zhijie Shen commented on YARN-292: -- Thanks for reviewing the patch, Junping! bq. However,

[jira] [Commented] (YARN-1055) Handle app recovery differently for AM failures and RM restart

[ https://issues.apache.org/jira/browse/YARN-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739372#comment-13739372 ] Karthik Kambatla commented on YARN-1055: bq. In case of a network issue where the A

[jira] [Commented] (YARN-292) ResourceManager throws ArrayIndexOutOfBoundsException while handling CONTAINER_ALLOCATED for application attempt

[ https://issues.apache.org/jira/browse/YARN-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739316#comment-13739316 ] Junping Du commented on YARN-292: - Also, I see you only address Fifo and Fair, but not addre

  1   2   >