[jira] [Commented] (YARN-8424) mapreduce job is getting submitted with negative priority as it is not handled to run with default priority(i.e: 0)

[ https://issues.apache.org/jira/browse/YARN-8424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523963#comment-16523963 ] Sunil Govindan commented on YARN-8424: -- In theory we can have integers. So there is ideally no

[jira] [Commented] (YARN-8423) GPU does not get released even though the application gets killed.

[ https://issues.apache.org/jira/browse/YARN-8423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523958#comment-16523958 ] Sunil Govindan commented on YARN-8423: -- YARN-8463 is created. Thanks [~leftnoteasy] > GPU does not

[jira] [Updated] (YARN-8435) NPE when the same client simultaneously contact for the first time Yarn Router

[ https://issues.apache.org/jira/browse/YARN-8435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giovanni Matteo Fumarola updated YARN-8435: --- Summary: NPE when the same client simultaneously contact for the first time

[jira] [Commented] (YARN-8214) Change default RegistryDNS port

[ https://issues.apache.org/jira/browse/YARN-8214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523903#comment-16523903 ] Eric Yang commented on YARN-8214: - Port 5335 is unregistered according to IANA. > Change default

[jira] [Commented] (YARN-8435) NPE when the same client simultaneously contact for the first time Yarn Router

[ https://issues.apache.org/jira/browse/YARN-8435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523919#comment-16523919 ] Giovanni Matteo Fumarola commented on YARN-8435: Thanks [~NeoMatrix] for the patch.

[jira] [Commented] (YARN-1013) CS should watch resource utilization of containers and allocate speculative containers if appropriate

[ https://issues.apache.org/jira/browse/YARN-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523921#comment-16523921 ] Íñigo Goiri commented on YARN-1013: --- Here I would do the same as in YARN-1015 to keep it consistent. We

[jira] [Created] (YARN-8463) Add more tests for GPU allocation and release scenarios

Sunil Govindan created YARN-8463: Summary: Add more tests for GPU allocation and release scenarios Key: YARN-8463 URL: https://issues.apache.org/jira/browse/YARN-8463 Project: Hadoop YARN

[jira] [Commented] (YARN-8435) NullPointerException when client first time connect to Yarn Router

[ https://issues.apache.org/jira/browse/YARN-8435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523764#comment-16523764 ] genericqa commented on YARN-8435: - | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-8462) Resource Manager shutdown with FATAL Exception

[ https://issues.apache.org/jira/browse/YARN-8462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523790#comment-16523790 ] Jason Lowe commented on YARN-8462: -- It looks like the NPE is occurring here when

[jira] [Updated] (YARN-8462) Resource Manager shutdown with FATAL Exception

[ https://issues.apache.org/jira/browse/YARN-8462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-8462: - Component/s: capacity scheduler > Resource Manager shutdown with FATAL Exception >

[jira] [Commented] (YARN-8455) Add basic acl check for all TS v2 REST APIs

[ https://issues.apache.org/jira/browse/YARN-8455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523982#comment-16523982 ] Sunil Govindan commented on YARN-8455: -- I think this is the first step towards reaching to a complete

[jira] [Updated] (YARN-8214) Change default RegistryDNS port

[ https://issues.apache.org/jira/browse/YARN-8214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Billie Rinaldi updated YARN-8214: - Attachment: YARN-8214.3.patch > Change default RegistryDNS port > ---

[jira] [Commented] (YARN-8108) RM metrics rest API throws GSSException in kerberized environment

[ https://issues.apache.org/jira/browse/YARN-8108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524037#comment-16524037 ] Sunil Govindan commented on YARN-8108: -- cc [~eyang] [~vinodkv] pls help to review the change > RM

[jira] [Commented] (YARN-8459) Capacity Scheduler should properly handle container allocation on app/node when app/node being removed by scheduler

[ https://issues.apache.org/jira/browse/YARN-8459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524036#comment-16524036 ] Sunil Govindan commented on YARN-8459: -- Hi [~leftnoteasy] and [~cheersyang] This issue happens as

[jira] [Updated] (YARN-8452) FairScheduler.update can take long time if yarn.scheduler.fair.sizebasedweight is on

[ https://issues.apache.org/jira/browse/YARN-8452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-8452: - Attachment: YARN-8452.003.patch > FairScheduler.update can take long time if >

[jira] [Commented] (YARN-8108) RM metrics rest API throws GSSException in kerberized environment

[ https://issues.apache.org/jira/browse/YARN-8108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524081#comment-16524081 ] Eric Yang commented on YARN-8108: - [~sunilg], you are correct, the test case is intermittent and does not

[jira] [Commented] (YARN-8214) Change default RegistryDNS port

[ https://issues.apache.org/jira/browse/YARN-8214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524112#comment-16524112 ] Hudson commented on YARN-8214: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14482 (See

[jira] [Commented] (YARN-1013) CS should watch resource utilization of containers and allocate speculative containers if appropriate

[ https://issues.apache.org/jira/browse/YARN-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524129#comment-16524129 ] Haibo Chen commented on YARN-1013: -- To add a bit of context to YARN-1015 (or YARN-1011 as a whole), we

[jira] [Resolved] (YARN-8462) Resource Manager shutdown with FATAL Exception

[ https://issues.apache.org/jira/browse/YARN-8462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe resolved YARN-8462. -- Resolution: Duplicate > Resource Manager shutdown with FATAL Exception >

[jira] [Commented] (YARN-8462) Resource Manager shutdown with FATAL Exception

[ https://issues.apache.org/jira/browse/YARN-8462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524162#comment-16524162 ] Jason Lowe commented on YARN-8462: -- Great, thanks Wangda! I'll mark this as a duplicate of YARN-8193

[jira] [Updated] (YARN-8461) Support strict memory control on individual container with elastic control memory mechanism

[ https://issues.apache.org/jira/browse/YARN-8461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-8461: - Attachment: YARN-8461.01.patch > Support strict memory control on individual container with elastic

[jira] [Commented] (YARN-8461) Support strict memory control on individual container with elastic control memory mechanism

[ https://issues.apache.org/jira/browse/YARN-8461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523992#comment-16523992 ] Haibo Chen commented on YARN-8461: -- Thanks for the review, [~szegedim]! I have updated the patch to

[jira] [Commented] (YARN-8459) Capacity Scheduler should properly handle container allocation on app/node when app/node being removed by scheduler

[ https://issues.apache.org/jira/browse/YARN-8459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524057#comment-16524057 ] Wangda Tan commented on YARN-8459: -- [~cheersyang], According to our current locking design of

[jira] [Assigned] (YARN-6995) Improve use of ResourceNotFoundException in resource types code

[ https://issues.apache.org/jira/browse/YARN-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Szilard Nemeth reassigned YARN-6995: Assignee: Szilard Nemeth (was: Daniel Templeton) > Improve use of

[jira] [Commented] (YARN-6995) Improve use of ResourceNotFoundException in resource types code

[ https://issues.apache.org/jira/browse/YARN-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524135#comment-16524135 ] Szilard Nemeth commented on YARN-6995: -- As per our offline discussion with Daniel, I'm taking this

[jira] [Updated] (YARN-6995) Improve use of ResourceNotFoundException in resource types code

[ https://issues.apache.org/jira/browse/YARN-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Szilard Nemeth updated YARN-6995: - Attachment: YARN-6995.006.patch > Improve use of ResourceNotFoundException in resource types code

[jira] [Commented] (YARN-7708) [GPG] Load based policy generator

[ https://issues.apache.org/jira/browse/YARN-7708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524148#comment-16524148 ] Botong Huang commented on YARN-7708: v3 patch looks good to me. Can you fix the yetus complaints?

[jira] [Commented] (YARN-8214) Change default RegistryDNS port

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

[jira] [Commented] (YARN-8461) Support strict memory control on individual container with elastic control memory mechanism

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

[jira] [Commented] (YARN-8452) FairScheduler.update can take long time if yarn.scheduler.fair.sizebasedweight is on

[ https://issues.apache.org/jira/browse/YARN-8452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524035#comment-16524035 ] Miklos Szegedi commented on YARN-8452: -- Thank you for the review [~wilfreds]. I updated the patch. I

[jira] [Updated] (YARN-8452) FairScheduler.update can take long time if yarn.scheduler.fair.sizebasedweight is on

[ https://issues.apache.org/jira/browse/YARN-8452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-8452: - Attachment: YARN-8452.002.patch > FairScheduler.update can take long time if >

[jira] [Commented] (YARN-8379) Add an option to allow Capacity Scheduler preemption to balance satisfied queues

[ https://issues.apache.org/jira/browse/YARN-8379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524088#comment-16524088 ] Zian Chen commented on YARN-8379: - Quickly checked the failed UT, it's a rounding cap issue which makes

[jira] [Updated] (YARN-8461) Support strict memory control on individual container with elastic control memory mechanism

[ https://issues.apache.org/jira/browse/YARN-8461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-8461: - Attachment: YARN-8461.02.patch > Support strict memory control on individual container with elastic

[jira] [Commented] (YARN-8461) Support strict memory control on individual container with elastic control memory mechanism

[ https://issues.apache.org/jira/browse/YARN-8461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524106#comment-16524106 ] Haibo Chen commented on YARN-8461: -- I updated the patch again to address the unit test failure. >

[jira] [Commented] (YARN-8214) Change default RegistryDNS port

[ https://issues.apache.org/jira/browse/YARN-8214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523983#comment-16523983 ] Billie Rinaldi commented on YARN-8214: -- Sounds good to me! > Change default RegistryDNS port >

[jira] [Updated] (YARN-8452) FairScheduler.update can take long time if yarn.scheduler.fair.sizebasedweight is on

[ https://issues.apache.org/jira/browse/YARN-8452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-8452: - Attachment: YARN-8452.001.patch > FairScheduler.update can take long time if >

[jira] [Commented] (YARN-8108) RM metrics rest API throws GSSException in kerberized environment

[ https://issues.apache.org/jira/browse/YARN-8108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524082#comment-16524082 ] Larry McCay commented on YARN-8108: --- +1 for patch 2. > RM metrics rest API throws GSSException in

[jira] [Commented] (YARN-8379) Add an option to allow Capacity Scheduler preemption to balance satisfied queues

[ https://issues.apache.org/jira/browse/YARN-8379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524091#comment-16524091 ] Zian Chen commented on YARN-8379: - [~eepayne], thank you for the notice. Let me ask Wangda and Sunil to

[jira] [Comment Edited] (YARN-8214) Change default RegistryDNS port

[ https://issues.apache.org/jira/browse/YARN-8214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524090#comment-16524090 ] Eric Yang edited comment on YARN-8214 at 6/26/18 6:27 PM: -- +1 looks good to me. 

[jira] [Commented] (YARN-8452) FairScheduler.update can take long time if yarn.scheduler.fair.sizebasedweight is on

[ https://issues.apache.org/jira/browse/YARN-8452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524161#comment-16524161 ] genericqa commented on YARN-8452: - | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Updated] (YARN-8108) RM metrics rest API throws GSSException in kerberized environment

[ https://issues.apache.org/jira/browse/YARN-8108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Yang updated YARN-8108: Target Version/s: 3.2.0, 3.1.1 (was: 3.2.0, 3.1.1, 3.0.3) > RM metrics rest API throws GSSException in

[jira] [Assigned] (YARN-8108) RM metrics rest API throws GSSException in kerberized environment

[ https://issues.apache.org/jira/browse/YARN-8108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Yang reassigned YARN-8108: --- Assignee: Sunil Govindan (was: Eric Yang) > RM metrics rest API throws GSSException in kerberized

[jira] [Commented] (YARN-8103) Add CLI interface to query node attributes

[ https://issues.apache.org/jira/browse/YARN-8103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524084#comment-16524084 ] Naganarasimha G R commented on YARN-8103: - Thanks for the updated patch [~bibinchundatt],  latest

[jira] [Comment Edited] (YARN-8458) Perform SLS testing and run TestCapacitySchedulerPerf on trunk

[ https://issues.apache.org/jira/browse/YARN-8458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16522912#comment-16522912 ] Chandni Singh edited comment on YARN-8458 at 6/26/18 6:52 PM: -- *

[jira] [Commented] (YARN-8108) RM metrics rest API throws GSSException in kerberized environment

[ https://issues.apache.org/jira/browse/YARN-8108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524053#comment-16524053 ] Sunil Govindan commented on YARN-8108: -- Thanks [~eyang] This tests failed for fair scheduler. While

[jira] [Commented] (YARN-8461) Support strict memory control on individual container with elastic control memory mechanism

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

[jira] [Commented] (YARN-6964) Fair scheduler misuses Resources operations

[ https://issues.apache.org/jira/browse/YARN-6964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524153#comment-16524153 ] Szilard Nemeth commented on YARN-6964: -- Applied the latest patch to trunk, it compiles fine so my

[jira] [Commented] (YARN-8108) RM metrics rest API throws GSSException in kerberized environment

[ https://issues.apache.org/jira/browse/YARN-8108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524041#comment-16524041 ] Eric Yang commented on YARN-8108: - [~sunilg], thank you for the patch.  Patch 2 will remove the conflict

[jira] [Commented] (YARN-8462) Resource Manager shutdown with FATAL Exception

[ https://issues.apache.org/jira/browse/YARN-8462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524042#comment-16524042 ] Wangda Tan commented on YARN-8462: -- [~jlowe], it seems this issue is fixed by YARN-8193 already. >

[jira] [Commented] (YARN-1013) CS should watch resource utilization of containers and allocate speculative containers if appropriate

[ https://issues.apache.org/jira/browse/YARN-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524101#comment-16524101 ] Wangda Tan commented on YARN-1013: -- Just took a very quick look at YARN-1015. IIUC, scheduler allocates O

[jira] [Commented] (YARN-6482) TestSLSRunner runs but doesn't executed jobs (.json parsing issue)

[ https://issues.apache.org/jira/browse/YARN-6482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523264#comment-16523264 ] Junping Du commented on YARN-6482: -- Hi [~yuanbo], any plan to deliver a fix? > TestSLSRunner runs but

[jira] [Commented] (YARN-8434) Nodemanager not registering to active RM in federation

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

[jira] [Commented] (YARN-8459) Capacity Scheduler should properly handle container allocation on app/node when app/node being removed by scheduler

[ https://issues.apache.org/jira/browse/YARN-8459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523262#comment-16523262 ] Weiwei Yang commented on YARN-8459: --- Hi [~leftnoteasy] Both {{CapacityScheduler#removeNode}} and

[jira] [Commented] (YARN-1013) CS should watch resource utilization of containers and allocate speculative containers if appropriate

[ https://issues.apache.org/jira/browse/YARN-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523385#comment-16523385 ] Weiwei Yang commented on YARN-1013: --- Hi [~haibochen], [~elgoiri] I took a look at YARN-1015, it is a

[jira] [Commented] (YARN-8438) TestContainer.testKillOnNew flaky on trunk

[ https://issues.apache.org/jira/browse/YARN-8438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523285#comment-16523285 ] Szilard Nemeth commented on YARN-8438: -- Hi [~miklos.szeg...@cloudera.com]! Thanks for the review and

[jira] [Created] (YARN-8462) Resource Manager shutdown with FATAL Exception

Amithsha created YARN-8462: -- Summary: Resource Manager shutdown with FATAL Exception Key: YARN-8462 URL: https://issues.apache.org/jira/browse/YARN-8462 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-8462) Resource Manager shutdown with FATAL Exception

[ https://issues.apache.org/jira/browse/YARN-8462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amithsha updated YARN-8462: --- Priority: Critical (was: Major) > Resource Manager shutdown with FATAL Exception >

[jira] [Commented] (YARN-8462) Resource Manager shutdown with FATAL Exception

[ https://issues.apache.org/jira/browse/YARN-8462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523513#comment-16523513 ] Amithsha commented on YARN-8462: This is happening intermediately in-between 3 days. > Resource Manager

[jira] [Updated] (YARN-8424) mapreduce job is getting submitted with negative priority as it is not handled to run with default priority(i.e: 0)

[ https://issues.apache.org/jira/browse/YARN-8424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bakthavachalam updated YARN-8424: - Attachment: apppatch.patch > mapreduce job is getting submitted with negative priority as it is

[jira] [Updated] (YARN-8424) mapreduce job is getting submitted with negative priority as it is not handled to run with default priority(i.e: 0)

[ https://issues.apache.org/jira/browse/YARN-8424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bakthavachalam updated YARN-8424: - Attachment: (was: apppatch.patch) > mapreduce job is getting submitted with negative priority

[jira] [Updated] (YARN-8435) NullPointerException when client first time connect to Yarn Router

[ https://issues.apache.org/jira/browse/YARN-8435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] rangjiaheng updated YARN-8435: -- Attachment: YARN-8435.v3.patch > NullPointerException when client first time connect to Yarn Router >

[jira] [Commented] (YARN-8435) NullPointerException when client first time connect to Yarn Router

[ https://issues.apache.org/jira/browse/YARN-8435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523669#comment-16523669 ] rangjiaheng commented on YARN-8435: --- Thanks for [~giovanni.fumarola].  Already finished for 

[jira] [Commented] (YARN-6672) Add NM preemption of opportunistic containers when utilization goes high

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

[jira] [Updated] (YARN-8459) Capacity Scheduler should properly handle container allocation on app/node when app/node being removed by scheduler

[ https://issues.apache.org/jira/browse/YARN-8459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-8459: - Attachment: YARN-8459.002.patch > Capacity Scheduler should properly handle container allocation on

[jira] [Updated] (YARN-8464) Async scheduling thread could be interrupted when there are no NodeManagers in cluster

[ https://issues.apache.org/jira/browse/YARN-8464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-8464: - Fix Version/s: 3.2.0 > Async scheduling thread could be interrupted when there are no NodeManagers > in

[jira] [Commented] (YARN-8423) GPU does not get released even though the application gets killed.

[ https://issues.apache.org/jira/browse/YARN-8423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524496#comment-16524496 ] Hudson commented on YARN-8423: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14485 (See

[jira] [Commented] (YARN-8464) Async scheduling thread could be interrupted when there are no NodeManagers in cluster

[ https://issues.apache.org/jira/browse/YARN-8464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524497#comment-16524497 ] Hudson commented on YARN-8464: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14485 (See

[jira] [Commented] (YARN-8435) NPE when the same client simultaneously contact for the first time Yarn Router

[ https://issues.apache.org/jira/browse/YARN-8435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524539#comment-16524539 ] rangjiaheng commented on YARN-8435: --- Thanks [~giovanni.fumarola] for review. Javadoc for unit tests is

[jira] [Commented] (YARN-8379) Add an option to allow Capacity Scheduler preemption to balance satisfied queues

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

[jira] [Assigned] (YARN-7556) Fair scheduler configuration should allow resource types in the minResources and maxResources properties

[ https://issues.apache.org/jira/browse/YARN-7556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Szilard Nemeth reassigned YARN-7556: Assignee: Szilard Nemeth (was: Daniel Templeton) > Fair scheduler configuration should

[jira] [Updated] (YARN-7556) Fair scheduler configuration should allow resource types in the minResources and maxResources properties

[ https://issues.apache.org/jira/browse/YARN-7556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Szilard Nemeth updated YARN-7556: - Attachment: YARN-7556.008.patch > Fair scheduler configuration should allow resource types in the

[jira] [Updated] (YARN-8464) Application does not get to Running state even with available resources on node managers when async scheduling is enabled

[ https://issues.apache.org/jira/browse/YARN-8464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8464: Reporter: Charan Hebri (was: Sunil Govindan) > Application does not get to Running state

[jira] [Updated] (YARN-8464) Application does not get to Running state even with available resources on node managers when async scheduling is enabled

[ https://issues.apache.org/jira/browse/YARN-8464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-8464: - Attachment: YARN-8464.001.patch > Application does not get to Running state even with available

[jira] [Commented] (YARN-8464) Application does not get to Running state even with available resources on node managers when async scheduling is enabled

[ https://issues.apache.org/jira/browse/YARN-8464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524308#comment-16524308 ] Sunil Govindan commented on YARN-8464: -- Thanks [~leftnoteasy] for helping in debugging same.

[jira] [Updated] (YARN-6672) Add NM preemption of opportunistic containers when utilization goes high

[ https://issues.apache.org/jira/browse/YARN-6672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-6672: - Attachment: YARN-6672-YARN-1011.03.patch > Add NM preemption of opportunistic containers when utilization

[jira] [Commented] (YARN-7556) Fair scheduler configuration should allow resource types in the minResources and maxResources properties

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

[jira] [Comment Edited] (YARN-8409) ActiveStandbyElectorBasedElectorService is failing with NPE

[ https://issues.apache.org/jira/browse/YARN-8409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524290#comment-16524290 ] Chandni Singh edited comment on YARN-8409 at 6/27/18 12:51 AM: --- This happens

[jira] [Commented] (YARN-8258) YARN webappcontext for UI2 should inherit all filters from default context

[ https://issues.apache.org/jira/browse/YARN-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524396#comment-16524396 ] Sunil Govindan commented on YARN-8258: -- Test case failure is not related to this patch. YARN-7548 is

[jira] [Commented] (YARN-8258) YARN webappcontext for UI2 should inherit all filters from default context

[ https://issues.apache.org/jira/browse/YARN-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524407#comment-16524407 ] Sunil Govindan commented on YARN-8258: -- cc [~eyang] and [~vinodkv] > YARN webappcontext for UI2

[jira] [Commented] (YARN-7974) Allow updating application tracking url after registration

[ https://issues.apache.org/jira/browse/YARN-7974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524448#comment-16524448 ] Keqiu Hu commented on YARN-7974: [~leftnoteasy] could you please review this latest patch? (005) > Allow

[jira] [Commented] (YARN-8459) Capacity Scheduler should properly handle container allocation on app/node when app/node being removed by scheduler

[ https://issues.apache.org/jira/browse/YARN-8459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524476#comment-16524476 ] Weiwei Yang commented on YARN-8459: --- Hi [~leftnoteasy], [~sunilg] bq. c. Reserve on node operation

[jira] [Commented] (YARN-8464) Async scheduling thread could be interrupted when there are no NodeManagers in cluster

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

[jira] [Commented] (YARN-8466) Add Chaos Monkey unit test framework for feature validation in scale

[ https://issues.apache.org/jira/browse/YARN-8466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524431#comment-16524431 ] Weiwei Yang commented on YARN-8466: --- Hi [~leftnoteasy] Having that in UT sounds an easier approach but

[jira] [Commented] (YARN-8466) Add Chaos Monkey unit test framework for feature validation in scale

[ https://issues.apache.org/jira/browse/YARN-8466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1652#comment-1652 ] Sunil Govindan commented on YARN-8466: -- Thanks [~leftnoteasy] for proposing this and [~cheersyang]

[jira] [Commented] (YARN-8459) Capacity Scheduler should properly handle container allocation on app/node when app/node being removed by scheduler

[ https://issues.apache.org/jira/browse/YARN-8459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524472#comment-16524472 ] Wangda Tan commented on YARN-8459: -- Thanks [~sunilg], Addressed #1. For #2, it is required since we

[jira] [Commented] (YARN-8466) Add Chaos Monkey unit test framework for feature validation in scale

[ https://issues.apache.org/jira/browse/YARN-8466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524485#comment-16524485 ] Wangda Tan commented on YARN-8466: -- Thanks [~cheersyang], actually this JIRA is inspired by the

[jira] [Commented] (YARN-8462) Resource Manager shutdown with FATAL Exception

[ https://issues.apache.org/jira/browse/YARN-8462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524524#comment-16524524 ] Amithsha commented on YARN-8462: [~leftnoteasy] and [~jlowe] thanks for quick reply.  It will be helpful

[jira] [Commented] (YARN-8462) Resource Manager shutdown with FATAL Exception

[ https://issues.apache.org/jira/browse/YARN-8462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524528#comment-16524528 ] Amithsha commented on YARN-8462: + appInfo.*getAppPlacementAllocator*(schedulerKey); -

[jira] [Updated] (YARN-8435) NPE when the same client simultaneously contact for the first time Yarn Router

[ https://issues.apache.org/jira/browse/YARN-8435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] rangjiaheng updated YARN-8435: -- Attachment: YARN-8435.v4.patch > NPE when the same client simultaneously contact for the first time

[jira] [Commented] (YARN-8409) ActiveStandbyElectorBasedElectorService is failing with NPE

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

[jira] [Commented] (YARN-8214) Change default RegistryDNS port

[ https://issues.apache.org/jira/browse/YARN-8214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524253#comment-16524253 ] Billie Rinaldi commented on YARN-8214: -- Thanks for the review, [~eyang]! > Change default

[jira] [Commented] (YARN-8258) YARN webappcontext for UI2 should inherit all filters from default context

[ https://issues.apache.org/jira/browse/YARN-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524260#comment-16524260 ] Vinod Kumar Vavilapalli commented on YARN-8258: --- What about the Safari issue? Can you rerun

[jira] [Updated] (YARN-8461) Support strict memory control on individual container with elastic control memory mechanism

[ https://issues.apache.org/jira/browse/YARN-8461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-8461: - Attachment: YARN-8461.03.patch > Support strict memory control on individual container with elastic

[jira] [Created] (YARN-8464) Application does not get to Running state even with available resources on node managers when async scheduling is enabled

Sunil Govindan created YARN-8464: Summary: Application does not get to Running state even with available resources on node managers when async scheduling is enabled Key: YARN-8464 URL:

[jira] [Created] (YARN-8465) Dshell docker container gets marked as lost after NM restart

Yesha Vora created YARN-8465: Summary: Dshell docker container gets marked as lost after NM restart Key: YARN-8465 URL: https://issues.apache.org/jira/browse/YARN-8465 Project: Hadoop YARN

[jira] [Updated] (YARN-8464) Async scheduling thread could be interrupted when there are no NodeManagers in cluster

[ https://issues.apache.org/jira/browse/YARN-8464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-8464: - Priority: Blocker (was: Critical) > Async scheduling thread could be interrupted when there are no

[jira] [Commented] (YARN-6672) Add NM preemption of opportunistic containers when utilization goes high

[ https://issues.apache.org/jira/browse/YARN-6672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524371#comment-16524371 ] Haibo Chen commented on YARN-6672: -- Thanks for the review, [~elgoiri]! I updated the patch to address

[jira] [Commented] (YARN-8258) YARN webappcontext for UI2 should inherit all filters from default context

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

[jira] [Updated] (YARN-8379) Add an option to allow Capacity Scheduler preemption to balance satisfied queues

[ https://issues.apache.org/jira/browse/YARN-8379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zian Chen updated YARN-8379: Attachment: YARN-8379.005.patch > Add an option to allow Capacity Scheduler preemption to balance satisfied

[jira] [Commented] (YARN-8379) Add an option to allow Capacity Scheduler preemption to balance satisfied queues

[ https://issues.apache.org/jira/browse/YARN-8379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524393#comment-16524393 ] Zian Chen commented on YARN-8379: - [~sunilg], thanks for the comments. here is the updates for the latest

  1   2   >