[jira] [Updated] (YARN-386) [Umbrella] YARN API cleanup

[ https://issues.apache.org/jira/browse/YARN-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-386: - Priority: Major (was: Blocker) > [Umbrella] YARN API cleanup > ---

[jira] [Updated] (YARN-117) Enhance YARN service model

[ https://issues.apache.org/jira/browse/YARN-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-117: - Priority: Major (was: Blocker) > Enhance YARN service model >

[jira] [Updated] (YARN-397) RM Scheduler api enhancements

[ https://issues.apache.org/jira/browse/YARN-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-397: - Priority: Major (was: Blocker) > RM Scheduler api enhancements > -

[jira] [Updated] (YARN-414) [Umbrella] Usability issues in YARN

[ https://issues.apache.org/jira/browse/YARN-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-414: - Priority: Major (was: Blocker) > [Umbrella] Usability issues in YARN > ---

[jira] [Updated] (YARN-69) RM should throw different exceptions for while querying app/node/queue

[ https://issues.apache.org/jira/browse/YARN-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-69: Priority: Major (was: Blocker) > RM should throw different exceptions for while q

[jira] [Updated] (YARN-41) The RM should handle the graceful shutdown of the NM.

[ https://issues.apache.org/jira/browse/YARN-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-41: Priority: Major (was: Blocker) > The RM should handle the graceful shutdown of th

[jira] [Updated] (YARN-99) Jobs fail during resource localization when directories in file cache reaches to unix directory limit

[ https://issues.apache.org/jira/browse/YARN-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-99: Priority: Major (was: Blocker) > Jobs fail during resource localization when dire

[jira] [Updated] (YARN-34) Split/Cleanup YARN and MAPREDUCE documentation

[ https://issues.apache.org/jira/browse/YARN-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-34: Priority: Major (was: Blocker) > Split/Cleanup YARN and MAPREDUCE documentation >

[jira] [Updated] (YARN-226) Log aggregation should not assume an AppMaster will have containerId 1

[ https://issues.apache.org/jira/browse/YARN-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-226: - Priority: Major (was: Blocker) > Log aggregation should not assume an AppMaste

[jira] [Updated] (YARN-47) Security issues in YARN

[ https://issues.apache.org/jira/browse/YARN-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-47: Priority: Major (was: Blocker) > Security issues in YARN > -

[jira] [Updated] (YARN-396) Rationalize AllocateResponse in RM scheduler API

[ https://issues.apache.org/jira/browse/YARN-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-396: - Priority: Major (was: Blocker) > Rationalize AllocateResponse in RM scheduler

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

[ https://issues.apache.org/jira/browse/YARN-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583823#comment-13583823 ] Hitesh Shah commented on YARN-196: -- Patch still has trailing whitespace issues. In YarnCon

[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=13583792#comment-13583792 ] Sandy Ryza commented on YARN-392: - The proposal of per-app delay-scheduling parameters is on

[jira] [Updated] (YARN-47) Security issues in YARN

[ https://issues.apache.org/jira/browse/YARN-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-47: Priority: Blocker (was: Major) > Security issues in YARN > > >

[jira] [Updated] (YARN-226) Log aggregation should not assume an AppMaster will have containerId 1

[ https://issues.apache.org/jira/browse/YARN-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-226: - Priority: Blocker (was: Major) > Log aggregation should not assume an AppMaster will have containerId

[jira] [Updated] (YARN-71) Ensure/confirm that the NodeManager cleanup their local filesystem when they restart

[ https://issues.apache.org/jira/browse/YARN-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-71: Priority: Critical (was: Major) > Ensure/confirm that the NodeManager cleanup their local filesystem when

[jira] [Updated] (YARN-71) Ensure/confirm that the NodeManager cleanup their local filesystem when they restart

[ https://issues.apache.org/jira/browse/YARN-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-71: Issue Type: Bug (was: Test) > Ensure/confirm that the NodeManager cleanup their local filesystem when the

[jira] [Updated] (YARN-396) Rationalize AllocateResponse in RM scheduler API

[ https://issues.apache.org/jira/browse/YARN-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-396: - Priority: Blocker (was: Major) > Rationalize AllocateResponse in RM scheduler API > --

[jira] [Updated] (YARN-387) Fix inconsistent protocol naming

[ https://issues.apache.org/jira/browse/YARN-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-387: - Priority: Blocker (was: Major) > Fix inconsistent protocol naming > >

[jira] [Updated] (YARN-378) ApplicationMaster retry times should be set by Client

[ https://issues.apache.org/jira/browse/YARN-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-378: - Priority: Major (was: Minor) > ApplicationMaster retry times should be set by Client > ---

[jira] [Updated] (YARN-34) Split/Cleanup YARN and MAPREDUCE documentation

[ https://issues.apache.org/jira/browse/YARN-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-34: Priority: Blocker (was: Major) > Split/Cleanup YARN and MAPREDUCE documentation > ---

[jira] [Updated] (YARN-99) Jobs fail during resource localization when directories in file cache reaches to unix directory limit

[ https://issues.apache.org/jira/browse/YARN-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-99: Priority: Blocker (was: Major) > Jobs fail during resource localization when directories in file cache re

[jira] [Updated] (YARN-117) Enhance YARN service model

[ https://issues.apache.org/jira/browse/YARN-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-117: - Priority: Blocker (was: Major) > Enhance YARN service model > -- > >

[jira] [Updated] (YARN-85) Allow per job log aggregation configuration

[ https://issues.apache.org/jira/browse/YARN-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-85: Priority: Critical (was: Major) > Allow per job log aggregation configuration > -

[jira] [Updated] (YARN-142) Change YARN APIs to throw IOException

[ https://issues.apache.org/jira/browse/YARN-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-142: - Priority: Blocker (was: Critical) > Change YARN APIs to throw IOException > --

[jira] [Updated] (YARN-69) RM should throw different exceptions for while querying app/node/queue

[ https://issues.apache.org/jira/browse/YARN-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-69: Priority: Blocker (was: Major) > RM should throw different exceptions for while querying app/node/queue >

[jira] [Updated] (YARN-41) The RM should handle the graceful shutdown of the NM.

[ https://issues.apache.org/jira/browse/YARN-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-41: Priority: Blocker (was: Major) > The RM should handle the graceful shutdown of the NM. >

[jira] [Updated] (YARN-270) RM scheduler event handler thread gets behind

[ https://issues.apache.org/jira/browse/YARN-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-270: - Priority: Blocker (was: Major) > RM scheduler event handler thread gets behind > -

[jira] [Updated] (YARN-386) [Umbrella] YARN API cleanup

[ https://issues.apache.org/jira/browse/YARN-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-386: - Priority: Blocker (was: Major) > [Umbrella] YARN API cleanup > --- > >

[jira] [Updated] (YARN-397) RM Scheduler api enhancements

[ https://issues.apache.org/jira/browse/YARN-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-397: - Priority: Blocker (was: Major) > RM Scheduler api enhancements > - > >

[jira] [Updated] (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 ] Hitesh Shah updated YARN-404: - Priority: Blocker (was: Critical) > Node Manager leaks Data Node connections > ---

[jira] [Created] (YARN-414) [Umbrella] Usability issues in YARN

Hitesh Shah created YARN-414: Summary: [Umbrella] Usability issues in YARN Key: YARN-414 URL: https://issues.apache.org/jira/browse/YARN-414 Project: Hadoop YARN Issue Type: Bug Repor

[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=13583713#comment-13583713 ] Bikas Saha commented on YARN-392: - >From what I understand this seems to be tangentially goi

[jira] [Resolved] (YARN-413) With log aggregation on, nodemanager dies on startup if it can't connect to HDFS

[ https://issues.apache.org/jira/browse/YARN-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe resolved YARN-413. - Resolution: Duplicate > With log aggregation on, nodemanager dies on startup if it can't connect to >

[jira] [Commented] (YARN-413) With log aggregation on, nodemanager dies on startup if it can't connect to HDFS

[ https://issues.apache.org/jira/browse/YARN-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583660#comment-13583660 ] Sandy Ryza commented on YARN-413: - 2013-02-21 13:27:24,307 FATAL org.apache.hadoop.yarn.ser

[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=13583651#comment-13583651 ] Alejandro Abdelnur commented on YARN-392: - I think the 2nd approach (introducing an

[jira] [Commented] (YARN-408) Capacity Scheduler delay scheduling should not be disabled by default

[ https://issues.apache.org/jira/browse/YARN-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583625#comment-13583625 ] Mayank Bansal commented on YARN-408: Yeah sure. There are two intents to change this va

[jira] [Created] (YARN-413) With log aggregation on, nodemanager dies on startup if it can't connect to HDFS

Sandy Ryza created YARN-413: --- Summary: With log aggregation on, nodemanager dies on startup if it can't connect to HDFS Key: YARN-413 URL: https://issues.apache.org/jira/browse/YARN-413 Project: Hadoop YARN

[jira] [Commented] (YARN-412) FifoScheduler incorrectly checking for node locality

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

[jira] [Updated] (YARN-412) FifoScheduler incorrectly checking for node locality

[ https://issues.apache.org/jira/browse/YARN-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Hoover updated YARN-412: -- Attachment: YARN-412.patch Added a timeout on the unit test > FifoScheduler incorrectly

[jira] [Updated] (YARN-412) FifoScheduler incorrectly checking for node locality

[ https://issues.apache.org/jira/browse/YARN-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Hoover updated YARN-412: -- Attachment: (was: YARN-412.patch) > FifoScheduler incorrectly checking for node locality > --

[jira] [Commented] (YARN-412) FifoScheduler incorrectly checking for node locality

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

[jira] [Updated] (YARN-412) FifoScheduler incorrectly checking for node locality

[ https://issues.apache.org/jira/browse/YARN-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Hoover updated YARN-412: -- Description: In the FifoScheduler, the assignNodeLocalContainers method is checking if the data is local

[jira] [Updated] (YARN-412) FifoScheduler incorrectly checking for node locality

[ https://issues.apache.org/jira/browse/YARN-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Hoover updated YARN-412: -- Attachment: YARN-412.patch Please review this patch for the fix plus a unit test case >

[jira] [Created] (YARN-412) FifoScheduler incorrectly checking for node locality

Roger Hoover created YARN-412: - Summary: FifoScheduler incorrectly checking for node locality Key: YARN-412 URL: https://issues.apache.org/jira/browse/YARN-412 Project: Hadoop YARN Issue Type: Bu

[jira] [Moved] (YARN-411) Per-state RM app-pages should have search ala JHS pages

[ https://issues.apache.org/jira/browse/YARN-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli moved MAPREDUCE-3778 to YARN-411: - Component/s: (was: webapps)

[jira] [Updated] (YARN-69) RM should throw different exceptions for while querying app/node/queue

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

[jira] [Updated] (YARN-410) Miscellaneous web UI issues

[ https://issues.apache.org/jira/browse/YARN-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-410: - Labels: usability (was: ) > Miscellaneous web UI issues >

[jira] [Moved] (YARN-410) Miscellaneous web UI issues

[ https://issues.apache.org/jira/browse/YARN-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli moved MAPREDUCE-3152 to YARN-410: - Component/s: (was: mrv2) Fix Versi

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

[ https://issues.apache.org/jira/browse/YARN-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-237: - Labels: usability (was: ) > Refreshing the RM page forgets how many rows I had

[jira] [Updated] (YARN-198) If we are navigating to Nodemanager UI from Resourcemanager,then there is not link to navigate back to Resource manager

[ https://issues.apache.org/jira/browse/YARN-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-198: - Labels: usability (was: ) > If we are navigating to Nodemanager UI from Resour

[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 ] Vinod Kumar Vavilapalli updated YARN-379: - Labels: usability (was: ) > yarn [node,application] command print logger info

[jira] [Updated] (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 ] Vinod Kumar Vavilapalli updated YARN-380: - Labels: usability (was: ) > yarn node -status prints Last-Last-Node-Status > -

[jira] [Commented] (YARN-236) RM should point tracking URL to RM web page when app fails to start

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

[jira] [Commented] (YARN-400) RM can return null application resource usage report leading to NPE in client

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

[jira] [Commented] (YARN-236) RM should point tracking URL to RM web page when app fails to start

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

[jira] [Commented] (YARN-400) RM can return null application resource usage report leading to NPE in client

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

[jira] [Commented] (YARN-400) RM can return null application resource usage report leading to NPE in client

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

[jira] [Commented] (YARN-236) RM should point tracking URL to RM web page when app fails to start

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

[jira] [Commented] (YARN-236) RM should point tracking URL to RM web page when app fails to start

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

[jira] [Commented] (YARN-400) RM can return null application resource usage report leading to NPE in client

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