[jira] [Commented] (YARN-2071) Enforce more restricted permissions for the directory of Leveldb store

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

[jira] [Commented] (YARN-2059) Extend access control for admin acls

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

[jira] [Commented] (YARN-2096) Race in TestRMRestart#testQueueMetricsOnRMRestart

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

[jira] [Commented] (YARN-2073) Fair Scheduler: Add a utilization threshold to prevent preempting resources when cluster is free

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

[jira] [Commented] (YARN-1937) Add entity-level access control of the timeline data for owners only

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

[jira] [Commented] (YARN-2012) Fair Scheduler: allow default queue placement rule to take an arbitrary queue

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

[jira] [Commented] (YARN-1368) Common work to re-populate containers’ state into scheduler

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

[jira] [Commented] (YARN-1368) Common work to re-populate containers’ state into scheduler

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

[jira] [Commented] (YARN-2065) AM cannot create new containers after restart-NM token from previous attempt used

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

[jira] [Commented] (YARN-1368) Common work to re-populate containers’ state into scheduler

[ https://issues.apache.org/jira/browse/YARN-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14008538#comment-14008538 ] Wangda Tan commented on YARN-1368: -- [~jianhe], Thanks for addressing my comments, two more

[jira] [Commented] (YARN-149) ResourceManager (RM) High-Availability (HA)

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

[jira] [Updated] (YARN-2083) In fair scheduler, Queue should not been assigned more containers when its usedResource had reach the maxResource limit

[ https://issues.apache.org/jira/browse/YARN-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Tian updated YARN-2083: -- Attachment: YARN-2083.patch > In fair scheduler, Queue should not been assigned more containers when its > used

[jira] [Updated] (YARN-2083) In fair scheduler, Queue should not been assigned more containers when its usedResource had reach the maxResource limit

[ https://issues.apache.org/jira/browse/YARN-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Tian updated YARN-2083: -- Attachment: (was: YARN-2083.patch) > In fair scheduler, Queue should not been assigned more containers when

[jira] [Updated] (YARN-1000) Dynamic resource configuration feature can be configured to enable or disable and persistent on setting or not

[ https://issues.apache.org/jira/browse/YARN-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kenji Kikushima updated YARN-1000: -- Attachment: YARN-1000-sample.patch Attached file is sample implementation to switch dynamic reso

[jira] [Commented] (YARN-2083) In fair scheduler, Queue should not been assigned more containers when its usedResource had reach the maxResource limit

[ https://issues.apache.org/jira/browse/YARN-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14008571#comment-14008571 ] Yi Tian commented on YARN-2083: --- I think "precheck" is better than "aftercheck". And I think

[jira] [Commented] (YARN-1408) Preemption caused Invalid State Event: ACQUIRED at KILLED and caused a task timeout for 30mins

[ https://issues.apache.org/jira/browse/YARN-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14008576#comment-14008576 ] Sunil G commented on YARN-1408: --- Yes. As I mentioned in earlier comment, it is better to add

[jira] [Commented] (YARN-2083) In fair scheduler, Queue should not been assigned more containers when its usedResource had reach the maxResource limit

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

[jira] [Commented] (YARN-1911) NullPointerException in ResourceOption.getOverCommitTimeout()

[ https://issues.apache.org/jira/browse/YARN-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14008608#comment-14008608 ] Binglin Chang commented on YARN-1911: - +1, I also got this bug when doing YARN-2051, ho

[jira] [Created] (YARN-2103) Fix code bug in SerializedExceptionPBImpl

Binglin Chang created YARN-2103: --- Summary: Fix code bug in SerializedExceptionPBImpl Key: YARN-2103 URL: https://issues.apache.org/jira/browse/YARN-2103 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-2051) Fix code bug and add more unit tests for PBImpls

[ https://issues.apache.org/jira/browse/YARN-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Binglin Chang updated YARN-2051: Summary: Fix code bug and add more unit tests for PBImpls (was: Add more unit tests for PBImpl that