[jira] [Commented] (YARN-1927) Preemption message shouldn’t be created multiple times for same container-id in ProportionalCapacityPreemptionPolicy

[ https://issues.apache.org/jira/browse/YARN-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13967706#comment-13967706 ] Wangda Tan commented on YARN-1927: -- Hi [~chris.douglas], thanks for your jumping in for th

[jira] [Commented] (YARN-1927) Preemption message shouldn’t be created multiple times for same container-id in ProportionalCapacityPreemptionPolicy

[ https://issues.apache.org/jira/browse/YARN-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13967685#comment-13967685 ] Chris Douglas commented on YARN-1927: - The decision to preempt a container may be rever

[jira] [Commented] (YARN-1934) Potential NPE in ZKRMStateStore caused by handling Disconnected event from ZK.

[ https://issues.apache.org/jira/browse/YARN-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13967581#comment-13967581 ] Karthik Kambatla commented on YARN-1934: Assigning to myself, will take a look earl

[jira] [Updated] (YARN-1934) Potential NPE in ZKRMStateStore caused by handling Disconnected event from ZK.

[ https://issues.apache.org/jira/browse/YARN-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1934: --- Target Version/s: 2.4.1 > Potential NPE in ZKRMStateStore caused by handling Disconnected even

[jira] [Assigned] (YARN-1934) Potential NPE in ZKRMStateStore caused by handling Disconnected event from ZK.

[ https://issues.apache.org/jira/browse/YARN-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla reassigned YARN-1934: -- Assignee: Karthik Kambatla > Potential NPE in ZKRMStateStore caused by handling Disconne

[jira] [Commented] (YARN-1923) Make FairScheduler resource ratio calculations terminate faster

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

[jira] [Commented] (YARN-1883) TestRMAdminService fails due to inconsistent entries in UserGroups

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

[jira] [Commented] (YARN-1907) TestRMApplicationHistoryWriter#testRMWritingMassiveHistory runs slow and intermittently fails

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

[jira] [Commented] (YARN-1833) TestRMAdminService Fails in trunk and branch-2 : Assert Fails due to different count of UserGroups for currentUser()

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

[jira] [Commented] (YARN-1907) TestRMApplicationHistoryWriter#testRMWritingMassiveHistory runs slow and intermittently fails

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

[jira] [Commented] (YARN-1883) TestRMAdminService fails due to inconsistent entries in UserGroups

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

[jira] [Commented] (YARN-1923) Make FairScheduler resource ratio calculations terminate faster

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

[jira] [Commented] (YARN-1833) TestRMAdminService Fails in trunk and branch-2 : Assert Fails due to different count of UserGroups for currentUser()

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

[jira] [Commented] (YARN-1907) TestRMApplicationHistoryWriter#testRMWritingMassiveHistory runs slow and intermittently fails

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

[jira] [Commented] (YARN-1883) TestRMAdminService fails due to inconsistent entries in UserGroups

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

[jira] [Commented] (YARN-1833) TestRMAdminService Fails in trunk and branch-2 : Assert Fails due to different count of UserGroups for currentUser()

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

[jira] [Commented] (YARN-1923) Make FairScheduler resource ratio calculations terminate faster

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

[jira] [Commented] (YARN-1922) Process group remains alive after container process is killed externally

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

[jira] [Updated] (YARN-1922) Process group remains alive after container process is killed externally

[ https://issues.apache.org/jira/browse/YARN-1922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-1922: - Component/s: nodemanager Affects Version/s: 2.4.0 > Process group remains alive after co

[jira] [Commented] (YARN-1932) Javascript injection on the job status page

[ https://issues.apache.org/jira/browse/YARN-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13967466#comment-13967466 ] Steve Loughran commented on YARN-1932: -- we really need a test for this to stop regress

[jira] [Commented] (YARN-1934) Potential NPE in ZKRMStateStore caused by handling Disconnected event from ZK.

[ https://issues.apache.org/jira/browse/YARN-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13967446#comment-13967446 ] Rohith commented on YARN-1934: -- Lets say zkClient session connected to server X. Killing/Stopp

[jira] [Commented] (YARN-1934) Potential NPE in ZKRMStateStore caused by handling Disconnected event from ZK.

[ https://issues.apache.org/jira/browse/YARN-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13967442#comment-13967442 ] Jian He commented on YARN-1934: --- there seems to be a race here. what causes the Disconnected

[jira] [Commented] (YARN-1934) Potential NPE in ZKRMStateStore caused by handling Disconnected event from ZK.

[ https://issues.apache.org/jira/browse/YARN-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13967437#comment-13967437 ] Rohith commented on YARN-1934: -- Call flow is attached file issue is 1. Disconnected event whi

[jira] [Updated] (YARN-1934) Potential NPE in ZKRMStateStore caused by handling Disconnected event from ZK.

[ https://issues.apache.org/jira/browse/YARN-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-1934: - Attachment: RM.txt Attached log file. > Potential NPE in ZKRMStateStore caused by handling Disconnected event fro

[jira] [Commented] (YARN-1924) STATE_STORE_OP_FAILED happens when ZKRMStateStore tries to update app(attempt) before storing it

[ https://issues.apache.org/jira/browse/YARN-1924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13967432#comment-13967432 ] Rohith commented on YARN-1924: -- I raised new Jira YARN-1934 for NPE. > STATE_STORE_OP_FAILED

[jira] [Created] (YARN-1934) Potential NPE in ZKRMStateStore caused by handling Disconnected event from ZK.

Rohith created YARN-1934: Summary: Potential NPE in ZKRMStateStore caused by handling Disconnected event from ZK. Key: YARN-1934 URL: https://issues.apache.org/jira/browse/YARN-1934 Project: Hadoop YARN

[jira] [Commented] (YARN-1931) Private API change in YARN-1824 in 2.4 broke compatibility with previous releases

[ https://issues.apache.org/jira/browse/YARN-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13967428#comment-13967428 ] Jian He commented on YARN-1931: --- bq. This was at best a clumsily written class with utilities