[jira] [Updated] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5392: -- Attachment: YARN-5392.003.patch Fixing testcases > Replace use of Priority in the Scheduling

[jira] [Commented] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15381715#comment-15381715 ] Hadoop QA commented on YARN-5392: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Updated] (YARN-5394) Correct the wrong file name when mounting /etc/passwd to Docker Container

[ https://issues.apache.org/jira/browse/YARN-5394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated YARN-5394: --- Attachment: YARN-5394-branch-2.8.001.patch Patch attached > Correct the wrong file name when mounting

[jira] [Updated] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5392: -- Attachment: YARN-5392.002.patch Modified patch to make the {{SchedulerKey}} constructor private and

[jira] [Created] (YARN-5394) Correct the wrong file name when mounting /etc/passwd to Docker Container

Zhankun Tang created YARN-5394: -- Summary: Correct the wrong file name when mounting /etc/passwd to Docker Container Key: YARN-5394 URL: https://issues.apache.org/jira/browse/YARN-5394 Project: Hadoop

[jira] [Updated] (YARN-5360) Decouple host user and Docker container user

[ https://issues.apache.org/jira/browse/YARN-5360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated YARN-5360: --- Description: There is *a dependency between job submitting user and the user in the Docker image* in

[jira] [Updated] (YARN-5360) Decouple host user and Docker container user

[ https://issues.apache.org/jira/browse/YARN-5360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated YARN-5360: --- Description: There is *a dependency between job submitting user and the user in the Docker image* in

[jira] [Commented] (YARN-5360) Decouple host user and Docker container user

[ https://issues.apache.org/jira/browse/YARN-5360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15381650#comment-15381650 ] Zhankun Tang commented on YARN-5360: Change the title from "use UID .." to "Decouple host user and

[jira] [Updated] (YARN-5360) Decouple host user and Docker container user

[ https://issues.apache.org/jira/browse/YARN-5360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated YARN-5360: --- Summary: Decouple host user and Docker container user (was: Use UID instead of user name to build the

[jira] [Commented] (YARN-5148) [YARN-3368] Add page to new YARN UI to view server side configurations/logs/JVM-metrics

[ https://issues.apache.org/jira/browse/YARN-5148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15381644#comment-15381644 ] Weiwei Yang commented on YARN-5148: --- Hello [~kaisasak] Do you think it's better to use a drop down list

[jira] [Commented] (YARN-1079) Fix progress bar for long-lived services in YARN

[ https://issues.apache.org/jira/browse/YARN-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15381636#comment-15381636 ] Weiwei Yang commented on YARN-1079: --- I noticed this issue has been addressed in YARN-5347, maybe this one

[jira] [Commented] (YARN-5360) Use UID instead of user name to build the Docker run command

[ https://issues.apache.org/jira/browse/YARN-5360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15381601#comment-15381601 ] Zhongyue Luo commented on YARN-5360: [~sidharta-s]"In general it is good practice to ensure that image

[jira] [Resolved] (YARN-3504) TestRMRestart fails occasionally in trunk

[ https://issues.apache.org/jira/browse/YARN-3504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-3504. --- Resolution: Duplicate Looks like that to me too, closing as dup oYARN-2871. >

[jira] [Created] (YARN-5393) [Umbrella] Optimize YARN tests runtime

Vinod Kumar Vavilapalli created YARN-5393: - Summary: [Umbrella] Optimize YARN tests runtime Key: YARN-5393 URL: https://issues.apache.org/jira/browse/YARN-5393 Project: Hadoop YARN

[jira] [Commented] (YARN-5261) Lease/Reclaim Extension to Yarn

[ https://issues.apache.org/jira/browse/YARN-5261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15381435#comment-15381435 ] Naganarasimha G R commented on YARN-5261: - Thanks [~subru], Even i had the same in my mind either

[jira] [Commented] (YARN-5375) invoke MockRM#drainEvents implicitly in MockRM methods to reduce test failures

[ https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15381434#comment-15381434 ] Hadoop QA commented on YARN-5375: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Updated] (YARN-5375) invoke MockRM#drainEvents implicitly in MockRM methods to reduce test failures

[ https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sandflee updated YARN-5375: --- Attachment: YARN-5375.02.patch > invoke MockRM#drainEvents implicitly in MockRM methods to reduce test

[jira] [Commented] (YARN-5006) ResourceManager quit due to ApplicationStateData exceed the limit size of znode in zk

[ https://issues.apache.org/jira/browse/YARN-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15381372#comment-15381372 ] Benoit Perroud commented on YARN-5006: -- The same behaviour occurs when a user submit a job with a

[jira] [Commented] (YARN-5375) invoke MockRM#drainEvents implicitly in MockRM methods to reduce test failures

[ https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15381347#comment-15381347 ] Hadoop QA commented on YARN-5375: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-5375) invoke MockRM#drainEvents implicitly in MockRM methods to reduce test failures

[ https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15381345#comment-15381345 ] sandflee commented on YARN-5375: there still had a very little chance that events are left in eventQueue

[jira] [Commented] (YARN-5375) invoke MockRM#drainEvents implicitly in MockRM methods to reduce test failures

[ https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15381341#comment-15381341 ] sandflee commented on YARN-5375: 1, add drainSchedulerEvents and drainStateStoreEvents to drainEvents 2,

[jira] [Updated] (YARN-5375) invoke MockRM#drainEvents implicitly in MockRM methods to reduce test failures

[ https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sandflee updated YARN-5375: --- Attachment: YARN-5375.01.patch > invoke MockRM#drainEvents implicitly in MockRM methods to reduce test

[jira] [Commented] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15381270#comment-15381270 ] Hadoop QA commented on YARN-5392: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Updated] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5392: -- Attachment: YARN-5392.001.patch Attaching initial patch > Replace use of Priority in the Scheduling