[jira] [Updated] (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:all-tabpanel ] Kenji Kikushima updated YARN-457: - Attachment: YARN-457-2.patch Sorry. I changed to call initLocalNewNodeReportList() before clearing

[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-tabpanelfocusedCommentId=13620705#comment-13620705 ] Sandy Ryza commented on YARN-392: - Ok, I will work on a patch for the non-blacklist

[jira] [Commented] (YARN-527) Local filecache mkdir fails

[ https://issues.apache.org/jira/browse/YARN-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13620711#comment-13620711 ] Knut O. Hellan commented on YARN-527: - There is really no difference in how the

[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-branch-2-b.patch coverage fix for yarn api -

[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-b.patch coverage fix for yarn api -

[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-tabpanelfocusedCommentId=13620843#comment-13620843 ] Aleksey Gorshkov commented on YARN-425: --- update patch for trunk

[jira] [Updated] (YARN-427) Coverage fix for org.apache.hadoop.yarn.server.api.*

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

[jira] [Commented] (YARN-427) Coverage fix for org.apache.hadoop.yarn.server.api.*

[ https://issues.apache.org/jira/browse/YARN-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13620845#comment-13620845 ] Aleksey Gorshkov commented on YARN-427: --- patch was update patch YARN-427-trunk-a.patch

[jira] [Updated] (YARN-465) fix coverage org.apache.hadoop.yarn.server.webproxy

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

[jira] [Updated] (YARN-465) fix coverage org.apache.hadoop.yarn.server.webproxy

[ https://issues.apache.org/jira/browse/YARN-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Gorshkov updated YARN-465: -- Attachment: YARN-465-trunk-a.patch fix coverage org.apache.hadoop.yarn.server.webproxy

[jira] [Commented] (YARN-465) fix coverage org.apache.hadoop.yarn.server.webproxy

[ https://issues.apache.org/jira/browse/YARN-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13620914#comment-13620914 ] Aleksey Gorshkov commented on YARN-465: --- patches updated patch YARN-465-trunk-a.patch

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

[ https://issues.apache.org/jira/browse/YARN-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13620913#comment-13620913 ] Steve Loughran commented on YARN-117: - I'm not seeing all those tests failing locally,

[jira] [Created] (YARN-535) TestUnmanagedAMLauncher can corrupt target/test-classes/yarn-site.xml during write phase, breaks later test runs

Steve Loughran created YARN-535: --- Summary: TestUnmanagedAMLauncher can corrupt target/test-classes/yarn-site.xml during write phase, breaks later test runs Key: YARN-535 URL:

[jira] [Commented] (YARN-535) TestUnmanagedAMLauncher can corrupt target/test-classes/yarn-site.xml during write phase, breaks later test runs

[ https://issues.apache.org/jira/browse/YARN-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13620974#comment-13620974 ] Steve Loughran commented on YARN-535: - {code}

[jira] [Commented] (YARN-528) Make IDs read only

[ https://issues.apache.org/jira/browse/YARN-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621023#comment-13621023 ] Robert Joseph Evans commented on YARN-528: -- OK, I understand now. I will try to

[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-527) Local filecache mkdir fails

[ https://issues.apache.org/jira/browse/YARN-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621042#comment-13621042 ] Vinod Kumar Vavilapalli commented on YARN-527: -- If it is the 32K limit that

[jira] [Updated] (YARN-430) Add HDFS based store for RM which manages the store using directories

[ https://issues.apache.org/jira/browse/YARN-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-430: - Summary: Add HDFS based store for RM which manages the store using directories

[jira] [Updated] (YARN-248) Security related work for RM restart

[ https://issues.apache.org/jira/browse/YARN-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-248: - Summary: Security related work for RM restart (was: Restore

[jira] [Commented] (YARN-458) YARN daemon addresses must be placed in many different configs

[ https://issues.apache.org/jira/browse/YARN-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621114#comment-13621114 ] Sandy Ryza commented on YARN-458: - Verified on a pseudo-distributed cluster that both the

[jira] [Updated] (YARN-193) Scheduler.normalizeRequest does not account for allocation requests that exceed maximumAllocation limits

[ https://issues.apache.org/jira/browse/YARN-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-193: - Attachment: YARN-193.13.patch Fix the twice setting bug and change default max vcores to 4.

[jira] [Commented] (YARN-99) Jobs fail during resource localization when private distributed-cache hits unix directory limits

[ https://issues.apache.org/jira/browse/YARN-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621128#comment-13621128 ] Omkar Vinit Joshi commented on YARN-99: --- Rebasing the patch as 467 is now committed.

[jira] [Assigned] (YARN-514) Delayed store operations should not result in RM unavailability for app submission

[ https://issues.apache.org/jira/browse/YARN-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen reassigned YARN-514: Assignee: Zhijie Shen (was: Bikas Saha) Delayed store operations should not result in RM

[jira] [Created] (YARN-536) Remove ContainerStatus, ContainerState from Container api interface as they will not be called by the container object

Xuan Gong created YARN-536: -- Summary: Remove ContainerStatus, ContainerState from Container api interface as they will not be called by the container object Key: YARN-536 URL:

[jira] [Assigned] (YARN-536) Remove ContainerStatus, ContainerState from Container api interface as they will not be called by the container object

[ https://issues.apache.org/jira/browse/YARN-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong reassigned YARN-536: -- Assignee: Xuan Gong Remove ContainerStatus, ContainerState from Container api interface as they

[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 ] Vinod Kumar Vavilapalli updated YARN-404: - Priority: Major (was: Blocker) Moving it off blocker status. Devaraj, can you

[jira] [Commented] (YARN-536) Remove ContainerStatus, ContainerState from Container api interface as they will not be called by the container object

[ https://issues.apache.org/jira/browse/YARN-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621180#comment-13621180 ] Xuan Gong commented on YARN-536: Remove getter and setter for ContainerState,

[jira] [Commented] (YARN-101) If the heartbeat message loss, the nodestatus info of complete container will loss too.

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

[jira] [Commented] (YARN-381) Improve FS docs

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

[jira] [Commented] (YARN-427) Coverage fix for org.apache.hadoop.yarn.server.api.*

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

[jira] [Commented] (YARN-465) fix coverage org.apache.hadoop.yarn.server.webproxy

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

[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-tabpanelfocusedCommentId=13621218#comment-13621218 ] Hadoop QA commented on YARN-425: {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-193) Scheduler.normalizeRequest does not account for allocation requests that exceed maximumAllocation limits

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

[jira] [Commented] (YARN-99) Jobs fail during resource localization when private distributed-cache hits unix directory limits

the latest attachment http://issues.apache.org/jira/secure/attachment/12576823/yarn-99-20130403.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 4 new

[jira] [Commented] (YARN-516) TestContainerLocalizer.testContainerLocalizerMain is failing

[ https://issues.apache.org/jira/browse/YARN-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621255#comment-13621255 ] Eli Collins commented on YARN-516: -- I reverted this change (and the initial HADOOP-9357

[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 FifoScheduler incorrectly checking for node locality

[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] [Updated] (YARN-99) Jobs fail during resource localization when private distributed-cache hits unix directory limits

Components: nodemanager Affects Versions: 3.0.0, 2.0.0-alpha Reporter: Devaraj K Assignee: Omkar Vinit Joshi Attachments: yarn-99-20130324.patch, yarn-99-20130403.1.patch, yarn-99-20130403.patch If we have multiple jobs which uses distributed

[jira] [Updated] (YARN-536) Remove ContainerStatus, ContainerState from Container api interface as they will not be called by the container object

[ https://issues.apache.org/jira/browse/YARN-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-536: --- Attachment: YARN-536.1.patch Remove ContainerStatus, ContainerState from Container api interface as they

[jira] [Created] (YARN-537) Waiting containers are not informed if private localization for a resource fails.

Omkar Vinit Joshi created YARN-537: -- Summary: Waiting containers are not informed if private localization for a resource fails. Key: YARN-537 URL: https://issues.apache.org/jira/browse/YARN-537

[jira] [Moved] (YARN-538) RM address DNS lookup can cause unnecessary slowness on every JHS page load

[ https://issues.apache.org/jira/browse/YARN-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur moved MAPREDUCE-5111 to YARN-538: Component/s: (was: jobhistoryserver) Affects

[jira] [Created] (YARN-539) Memory leak in case resource localization fails. LocalizedResource remains in memory.

Omkar Vinit Joshi created YARN-539: -- Summary: Memory leak in case resource localization fails. LocalizedResource remains in memory. Key: YARN-539 URL: https://issues.apache.org/jira/browse/YARN-539

[jira] [Commented] (YARN-458) YARN daemon addresses must be placed in many different configs

[ https://issues.apache.org/jira/browse/YARN-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621319#comment-13621319 ] Alejandro Abdelnur commented on YARN-458: - +1. Do we need to do this for HS as well?

[jira] [Commented] (YARN-516) TestContainerLocalizer.testContainerLocalizerMain is failing

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

[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-tabpanelfocusedCommentId=13621338#comment-13621338 ] Hadoop QA commented on YARN-412: {color:red}-1 overall{color}. Here are the results of

[jira] [Updated] (YARN-193) Scheduler.normalizeRequest does not account for allocation requests that exceed maximumAllocation limits

[ https://issues.apache.org/jira/browse/YARN-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-193: - Attachment: YARN-193.14.patch Fixed the buggy test

[jira] [Commented] (YARN-537) Waiting containers are not informed if private localization for a resource fails.

[ https://issues.apache.org/jira/browse/YARN-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621381#comment-13621381 ] Vinod Kumar Vavilapalli commented on YARN-537: -- Yup, I put in a comment long

[jira] [Updated] (YARN-539) LocalizedResources are leaked in memory in case resource localization fails

[ https://issues.apache.org/jira/browse/YARN-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-539: - Summary: LocalizedResources are leaked in memory in case resource localization

[jira] [Commented] (YARN-458) YARN daemon addresses must be placed in many different configs

[ https://issues.apache.org/jira/browse/YARN-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621385#comment-13621385 ] Vinod Kumar Vavilapalli commented on YARN-458: -- +1 for the patch after the

[jira] [Commented] (YARN-536) Remove ContainerStatus, ContainerState from Container api interface as they will not be called by the container object

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

[jira] [Commented] (YARN-535) TestUnmanagedAMLauncher can corrupt target/test-classes/yarn-site.xml during write phase, breaks later test runs

[ https://issues.apache.org/jira/browse/YARN-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621573#comment-13621573 ] Chris Nauroth commented on YARN-535: {{TestDistributedShell#setup}} has nearly identical

[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] [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 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-tabpanelfocusedCommentId=13621709#comment-13621709 ] Hitesh Shah commented on YARN-412: -- @Roger, for future reference ( may not be applicable to

[jira] [Commented] (YARN-536) Remove ContainerStatus, ContainerState from Container api interface as they will not be called by the container object

[ https://issues.apache.org/jira/browse/YARN-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621720#comment-13621720 ] Vinod Kumar Vavilapalli commented on YARN-536: -- +1, this looks good. Checking

[jira] [Commented] (YARN-536) Remove ContainerStatus, ContainerState from Container api interface as they will not be called by the container object

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

[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-tabpanelfocusedCommentId=13621735#comment-13621735 ] Hadoop QA commented on YARN-412: {color:green}+1 overall{color}. Here are the results of