[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=13621878#comment-13621878 ] Knut O. Hellan commented on YARN-527: - Yes, this is a duplicate of YARN-467 so you may

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13622012#comment-13622012 ] Hudson commented on YARN-538: - Integrated in Hadoop-Yarn-trunk #174 (See

[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=13622015#comment-13622015 ] Hudson commented on YARN-516: - Integrated in Hadoop-Yarn-trunk #174 (See

[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=13622023#comment-13622023 ] Hudson commented on YARN-101: - Integrated in Hadoop-Yarn-trunk #174 (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=13622028#comment-13622028 ] Hudson commented on YARN-381: - Integrated in Hadoop-Yarn-trunk #174 (See

[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=13622029#comment-13622029 ] Hudson commented on YARN-536: - Integrated in Hadoop-Yarn-trunk #174 (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=13622154#comment-13622154 ] Hudson commented on YARN-381: - Integrated in Hadoop-Hdfs-trunk #1363 (See

[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=13622155#comment-13622155 ] Hudson commented on YARN-536: - Integrated in Hadoop-Hdfs-trunk #1363 (See

[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=13622145#comment-13622145 ] Hudson commented on YARN-458: - Integrated in Hadoop-Hdfs-trunk #1363 (See

[jira] [Commented] (YARN-382) SchedulerUtils improve way normalizeRequest sets the resource capabilities

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

[jira] [Created] (YARN-541) getAllocatedContainers() is not returning all the allocated containers

Krishna Kishore Bonagiri created YARN-541: - Summary: getAllocatedContainers() is not returning all the allocated containers Key: YARN-541 URL: https://issues.apache.org/jira/browse/YARN-541

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13622138#comment-13622138 ] Hudson commented on YARN-538: - Integrated in Hadoop-Hdfs-trunk #1363 (See

[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=13622344#comment-13622344 ] Hudson commented on YARN-101: - Integrated in Hadoop-Mapreduce-trunk #1390 (See

[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=13622350#comment-13622350 ] Hudson commented on YARN-536: - Integrated in Hadoop-Mapreduce-trunk #1390 (See

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

[ https://issues.apache.org/jira/browse/YARN-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-527. -- Resolution: Duplicate Closing as duplicates as per comments above.

[jira] [Updated] (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:all-tabpanel ] Arun C Murthy updated YARN-398: --- Attachment: YARN-398.patch I got this done on a long flight a week or two ago... needs more testing

[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=13622558#comment-13622558 ] Arun C Murthy commented on YARN-392: [~bikassaha] I'm against using timers for

[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=13622561#comment-13622561 ] Arun C Murthy commented on YARN-392: To be clear, the approach I took on YARN-398 allows

[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=13622563#comment-13622563 ] Arun C Murthy commented on YARN-392: Also, it allows for I want 'one container on any

[jira] [Updated] (YARN-525) make CS node-locality-delay refreshable

[ https://issues.apache.org/jira/browse/YARN-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated YARN-525: --- Assignee: Thomas Graves make CS node-locality-delay refreshable

[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=13622584#comment-13622584 ] Bikas Saha commented on YARN-392: - bq. I'm against using timers for specifying locality

[jira] [Updated] (YARN-495) Change NM behavior of reboot to resync

[ https://issues.apache.org/jira/browse/YARN-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-495: Summary: Change NM behavior of reboot to resync (was: Containers are not terminated when the NM is

[jira] [Updated] (YARN-529) MR job succeeds and exits even when unregister with RM fails

[ https://issues.apache.org/jira/browse/YARN-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-529: Summary: MR job succeeds and exits even when unregister with RM fails (was: Succeeded MR job is retried by

[jira] [Commented] (YARN-540) RM state store not cleaned if job succeeds but RM shutdown and restart-dispatcher stopped before it can process REMOVE_APP event

[ https://issues.apache.org/jira/browse/YARN-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622681#comment-13622681 ] Bikas Saha commented on YARN-540: - This is a known issue. The problem here is that the rm

[jira] [Commented] (YARN-534) AM max attempts is not checked when RM restart and try to recover attempts

[ https://issues.apache.org/jira/browse/YARN-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622685#comment-13622685 ] Bikas Saha commented on YARN-534: - Turns out that the max attempts limit is checked when job

[jira] [Assigned] (YARN-542) Change the default AM retry value to be not one

[ https://issues.apache.org/jira/browse/YARN-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reassigned YARN-542: Assignee: Vinod Kumar Vavilapalli Change the default AM retry value to

[jira] [Updated] (YARN-493) NodeManager job control logic flaws on Windows

[ https://issues.apache.org/jira/browse/YARN-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated YARN-493: --- Attachment: YARN-493.3.patch Here is a new patch that renames the new {{Shell}} methods to

[jira] [Updated] (YARN-525) make CS node-locality-delay refreshable

[ https://issues.apache.org/jira/browse/YARN-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated YARN-525: --- Attachment: YARN-525-branch-0.23.patch make CS node-locality-delay refreshable

[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=13622765#comment-13622765 ] Sandy Ryza commented on YARN-392: - [~acmurthy], that makes sense to me. We can use this one

[jira] [Commented] (YARN-493) NodeManager job control logic flaws on Windows

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

[jira] [Updated] (YARN-525) make CS node-locality-delay refreshable

[ https://issues.apache.org/jira/browse/YARN-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated YARN-525: --- Attachment: YARN-525.patch added unit test and include patch for trunk and branch-2.

[jira] [Commented] (YARN-479) NM retry behavior for connection to RM should be similar for lost heartbeats

[ https://issues.apache.org/jira/browse/YARN-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622783#comment-13622783 ] Bikas Saha commented on YARN-479: - I dont see the value of waitForever if we can specify a

[jira] [Commented] (YARN-196) Nodemanager should be more robust in handling connection failure to ResourceManager when a cluster is started

[ https://issues.apache.org/jira/browse/YARN-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622785#comment-13622785 ] Bikas Saha commented on YARN-196: - here is a finally block which will make the code sleeping

[jira] [Commented] (YARN-525) make CS node-locality-delay refreshable

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

[jira] [Commented] (YARN-470) Support a way to disable resource monitoring on the NodeManager

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

[jira] [Updated] (YARN-532) RMAdminProtocolPBClientImpl should implement Closeable

[ https://issues.apache.org/jira/browse/YARN-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated YARN-532: Attachment: YARN-532.txt LocalizationProtocol implementing Closeable as well.

[jira] [Updated] (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:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-99: Issue Type: Sub-task (was: Bug) Parent: YARN-543 Jobs fail during

[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: - Issue Type: Sub-task (was: Bug) Parent: YARN-543 LocalizedResources

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

[ https://issues.apache.org/jira/browse/YARN-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-543: - Component/s: nodemanager [Umbrella] NodeManager localization related issues

[jira] [Created] (YARN-544) Failed resource localization might introduce a race condition.

Omkar Vinit Joshi created YARN-544: -- Summary: Failed resource localization might introduce a race condition. Key: YARN-544 URL: https://issues.apache.org/jira/browse/YARN-544 Project: Hadoop YARN

[jira] [Commented] (YARN-532) RMAdminProtocolPBClientImpl should implement Closeable

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

[jira] [Updated] (YARN-479) NM retry behavior for connection to RM should be similar for lost heartbeats

[ https://issues.apache.org/jira/browse/YARN-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-479: - Attachment: YARN-479.6.patch NM retry behavior for connection to RM should be similar for lost heartbeats

[jira] [Commented] (YARN-479) NM retry behavior for connection to RM should be similar for lost heartbeats

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

[jira] [Commented] (YARN-544) Failed resource localization might introduce a race condition.

[ https://issues.apache.org/jira/browse/YARN-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622969#comment-13622969 ] Vinod Kumar Vavilapalli commented on YARN-544: -- When you come around to doing

[jira] [Updated] (YARN-544) Failed resource localization might introduce a race condition.

[ https://issues.apache.org/jira/browse/YARN-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-544: - Issue Type: Sub-task (was: Bug) Parent: YARN-543 Failed resource

[jira] [Commented] (YARN-532) RMAdminProtocolPBClientImpl should implement Closeable

[ https://issues.apache.org/jira/browse/YARN-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622972#comment-13622972 ] Vinod Kumar Vavilapalli commented on YARN-532: -- Looks good, checking it in.

[jira] [Commented] (YARN-532) RMAdminProtocolPBClientImpl should implement Closeable

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

[jira] [Commented] (YARN-493) NodeManager job control logic flaws on Windows

[ https://issues.apache.org/jira/browse/YARN-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622995#comment-13622995 ] Ivan Mitic commented on YARN-493: - +1, latest patch looks good to me, thanks Chris

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13623082#comment-13623082 ] Omkar Vinit Joshi commented on YARN-539: At present the flow of events in case

[jira] [Commented] (YARN-493) NodeManager job control logic flaws on Windows

[ https://issues.apache.org/jira/browse/YARN-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623084#comment-13623084 ] Chris Nauroth commented on YARN-493: Thank you for the reviews, Ivan!

[jira] [Commented] (YARN-493) NodeManager job control logic flaws on Windows

[ https://issues.apache.org/jira/browse/YARN-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623088#comment-13623088 ] Vinod Kumar Vavilapalli commented on YARN-493: -- Looking at this for final

[jira] [Updated] (YARN-479) NM retry behavior for connection to RM should be similar for lost heartbeats

[ https://issues.apache.org/jira/browse/YARN-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-479: - Attachment: YARN-479.7.patch fix conflicts with YARN-101 NM retry behavior for connection to RM

[jira] [Updated] (YARN-479) NM retry behavior for connection to RM should be similar for lost heartbeats

[ https://issues.apache.org/jira/browse/YARN-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-479: - Attachment: YARN-479.8.patch Add test case that nodeStatusUpdater will retry a fixed number of time and

[jira] [Commented] (YARN-479) NM retry behavior for connection to RM should be similar for lost heartbeats

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

[jira] [Updated] (YARN-157) The option shell_command and shell_script have conflict

[ https://issues.apache.org/jira/browse/YARN-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] rainy Yu updated YARN-157: -- Attachment: shell_script.sh YARN-157.patch Add unit test. Thank Vinod Kumar Vavilapalli for help

[jira] [Updated] (YARN-54) AggregatedLogFormat should be marked Private / Unstable

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

[jira] [Created] (YARN-547) New resource localization is tried even when Localized Resource is in DOWNLOADING state

Omkar Vinit Joshi created YARN-547: -- Summary: New resource localization is tried even when Localized Resource is in DOWNLOADING state Key: YARN-547 URL: https://issues.apache.org/jira/browse/YARN-547