[jira] [Updated] (YARN-9209) When nodePartition is not set in Placement Constraints, containers are allocated only in default partition

[ https://issues.apache.org/jira/browse/YARN-9209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tarun Parimi updated YARN-9209: --- Description: When application sets a placement constraint without specifying a nodePartition, the

[jira] [Updated] (YARN-9209) When nodePartition is not set in Placement Constraints, containers are allocated only in default partition

[ https://issues.apache.org/jira/browse/YARN-9209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tarun Parimi updated YARN-9209: --- Description: When application sets a placement constraint without specifying a nodePartition, the

[jira] [Created] (YARN-9209) When nodePartition is not set in Placement Constraints, containers are allocated only in default partition

Tarun Parimi created YARN-9209: -- Summary: When nodePartition is not set in Placement Constraints, containers are allocated only in default partition Key: YARN-9209 URL:

[jira] [Commented] (YARN-7976) [atsv2 read acls] REST API to list domain/domains

[ https://issues.apache.org/jira/browse/YARN-7976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745819#comment-16745819 ] Abhishek Modi commented on YARN-7976: - [~rohithsharma] [~vrushalic] could you please review it. I will

[jira] [Commented] (YARN-9204) yarn.scheduler.capacity..accessible-node-labels..capacity can not support absolute resource value

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

[jira] [Updated] (YARN-9204) yarn.scheduler.capacity..accessible-node-labels..capacity can not support absolute resource value

[ https://issues.apache.org/jira/browse/YARN-9204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiandan Yang updated YARN-9204: Attachment: YARN-9204.002.patch > > yarn.scheduler.capacity..accessible-node-labels..capacity >

[jira] [Commented] (YARN-9204) yarn.scheduler.capacity..accessible-node-labels..capacity can not support absolute resource value

[ https://issues.apache.org/jira/browse/YARN-9204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745806#comment-16745806 ] Jiandan Yang commented on YARN-9204: - Thanks [~leftnoteasy] I will add a UT and upload v2 patch. >

[jira] [Created] (YARN-9208) Distributed shell allow LocalResourceVisibility to be specified

Bibin A Chundatt created YARN-9208: -- Summary: Distributed shell allow LocalResourceVisibility to be specified Key: YARN-9208 URL: https://issues.apache.org/jira/browse/YARN-9208 Project: Hadoop YARN

[jira] [Commented] (YARN-9161) Absolute resources of capacity scheduler doesn't support GPU and FPGA

[ https://issues.apache.org/jira/browse/YARN-9161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745779#comment-16745779 ] Zac Zhou commented on YARN-9161: Update patch to fix failed UT cases > Absolute resources of capacity

[jira] [Updated] (YARN-9161) Absolute resources of capacity scheduler doesn't support GPU and FPGA

[ https://issues.apache.org/jira/browse/YARN-9161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zac Zhou updated YARN-9161: --- Attachment: YARN-9161.006.patch > Absolute resources of capacity scheduler doesn't support GPU and FPGA >

[jira] [Commented] (YARN-9205) When using custom resource type, application will fail to run due to the CapacityScheduler throws InvalidResourceRequestException(GREATER_THEN_MAX_ALLOCATION)

[ https://issues.apache.org/jira/browse/YARN-9205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745759#comment-16745759 ] Zac Zhou commented on YARN-9205: [~tangzhankun] {quote}private static Map

[jira] [Commented] (YARN-9195) RM Queue's pending container number might get decreased unexpectedly or even become negative once RM failover

[ https://issues.apache.org/jira/browse/YARN-9195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745757#comment-16745757 ] Shengyang Sha commented on YARN-9195: - [~leftnoteasy] Sure. I'm working on it and will submit a patch

[jira] [Commented] (YARN-9207) {Submarine} Support long-running service type services

[ https://issues.apache.org/jira/browse/YARN-9207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745752#comment-16745752 ] Xun Liu commented on YARN-9207: --- I saw an article here describing the service of a long service type.

[jira] [Commented] (YARN-9116) Capacity Scheduler: implements queue level maximum-allocation inheritance

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

[jira] [Commented] (YARN-9116) Capacity Scheduler: implements queue level maximum-allocation inheritance

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

[jira] [Created] (YARN-9207) {Submarine} Support long-running service type services

Xun Liu created YARN-9207: - Summary: {Submarine} Support long-running service type services Key: YARN-9207 URL: https://issues.apache.org/jira/browse/YARN-9207 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-9146) REST API to trigger storing auxiliary manifest file and publish to NMs

[ https://issues.apache.org/jira/browse/YARN-9146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745673#comment-16745673 ] Eric Yang commented on YARN-9146: - Can we check for null input and report bad request, if user request has

[jira] [Assigned] (YARN-9003) Support multi-homed network for docker container

[ https://issues.apache.org/jira/browse/YARN-9003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Yang reassigned YARN-9003: --- Assignee: (was: Eric Yang) > Support multi-homed network for docker container >

[jira] [Updated] (YARN-9194) Invalid event: REGISTERED and LAUNCH_FAILED at FAILED, and NullPointerException happens in RM while shutdown a NM

[ https://issues.apache.org/jira/browse/YARN-9194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-9194: - Fix Version/s: 3.1.3 3.2.1 3.3.0 > Invalid event: REGISTERED and

[jira] [Commented] (YARN-9206) RMServerUtils does not count SHUTDOWN as an accepted state

[ https://issues.apache.org/jira/browse/YARN-9206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745628#comment-16745628 ] Wangda Tan commented on YARN-9206: -- [~kshukla], could u please add a method to NodeState such as

[jira] [Updated] (YARN-9116) Capacity Scheduler: implements queue level maximum-allocation inheritance

[ https://issues.apache.org/jira/browse/YARN-9116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aihua Xu updated YARN-9116: --- Summary: Capacity Scheduler: implements queue level maximum-allocation inheritance (was: Capacity Scheduler:

[jira] [Commented] (YARN-9194) Invalid event: REGISTERED and LAUNCH_FAILED at FAILED, and NullPointerException happens in RM while shutdown a NM

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

[jira] [Commented] (YARN-9204) yarn.scheduler.capacity..accessible-node-labels..capacity can not support absolute resource value

[ https://issues.apache.org/jira/browse/YARN-9204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745625#comment-16745625 ] Wangda Tan commented on YARN-9204: -- [~yangjiandan], thanks, could you please provide a UT to prevent this

[jira] [Updated] (YARN-9116) Capacity Scheduler: add the default maximum-allocation-mb and maximum-allocation-vcores for the queues

[ https://issues.apache.org/jira/browse/YARN-9116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aihua Xu updated YARN-9116: --- Attachment: YARN-9116.3.patch > Capacity Scheduler: add the default maximum-allocation-mb and >

[jira] [Commented] (YARN-9195) RM Queue's pending container number might get decreased unexpectedly or even become negative once RM failover

[ https://issues.apache.org/jira/browse/YARN-9195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745611#comment-16745611 ] Wangda Tan commented on YARN-9195: -- [~ssy], thanks for filing the issue and provide analysis. We

[jira] [Commented] (YARN-9074) Docker container rm command should be executed after stop

[ https://issues.apache.org/jira/browse/YARN-9074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745607#comment-16745607 ] Wangda Tan commented on YARN-9074: -- [~shaneku...@gmail.com], could u get the patch committed if you're

[jira] [Commented] (YARN-9197) NPE in service AM when failed to launch container

[ https://issues.apache.org/jira/browse/YARN-9197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745606#comment-16745606 ] Wangda Tan commented on YARN-9197: -- Thanks [~kyungwan nam] for filing and working on the patch.

[jira] [Updated] (YARN-9206) RMServerUtils does not count SHUTDOWN as an accepted state

[ https://issues.apache.org/jira/browse/YARN-9206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kuhu Shukla updated YARN-9206: -- Attachment: YARN-9206.001.patch > RMServerUtils does not count SHUTDOWN as an accepted state >

[jira] [Commented] (YARN-9206) RMServerUtils does not count SHUTDOWN as an accepted state

[ https://issues.apache.org/jira/browse/YARN-9206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745595#comment-16745595 ] Kuhu Shukla commented on YARN-9206: --- Patch needs a test still, but just to get things going. >

[jira] [Created] (YARN-9206) RMServerUtils does not count SHUTDOWN as an accepted state

Kuhu Shukla created YARN-9206: - Summary: RMServerUtils does not count SHUTDOWN as an accepted state Key: YARN-9206 URL: https://issues.apache.org/jira/browse/YARN-9206 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-9205) When using custom resource type, application will fail to run due to the CapacityScheduler throws InvalidResourceRequestException(GREATER_THEN_MAX_ALLOCATION)

[ https://issues.apache.org/jira/browse/YARN-9205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745591#comment-16745591 ] Wangda Tan commented on YARN-9205: -- [~tangzhankun],  >From the log it looks like by design. There's a

[jira] [Commented] (YARN-9202) RM does not track nodes that are in the include list and never register

[ https://issues.apache.org/jira/browse/YARN-9202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745549#comment-16745549 ] Kuhu Shukla commented on YARN-9202: --- Thank you Jim for the review. Appreciate it. bq. If nodes are in

[jira] [Commented] (YARN-9202) RM does not track nodes that are in the include list and never register

[ https://issues.apache.org/jira/browse/YARN-9202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745516#comment-16745516 ] Jim Brennan commented on YARN-9202: --- [~kshukla] thanks for the patch! I'd like some clarification of

[jira] [Commented] (YARN-6616) YARN AHS shows submitTime for jobs same as startTime

[ https://issues.apache.org/jira/browse/YARN-6616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745492#comment-16745492 ] Eric Payne commented on YARN-6616: -- bq. I also wonder how this fix getting in would not break

[jira] [Commented] (YARN-9174) Backport YARN-7224 for refactoring of GpuDevice class

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

[jira] [Commented] (YARN-9191) Add cli option in DS to support enforceExecutionType in resource requests.

[ https://issues.apache.org/jira/browse/YARN-9191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745405#comment-16745405 ] Íñigo Goiri commented on YARN-9191: --- Thanks [~abmodi] for the test. You may want to add a limit to the

[jira] [Commented] (YARN-9184) Docker run doesn't pull down latest image if the image exists locally

[ https://issues.apache.org/jira/browse/YARN-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745373#comment-16745373 ] Eric Badger commented on YARN-9184: --- Thanks for the update, [~uranus]! {noformat} +if

[jira] [Commented] (YARN-8489) Need to support "dominant" component concept inside YARN service

[ https://issues.apache.org/jira/browse/YARN-8489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745363#comment-16745363 ] Suma Shivaprasad commented on YARN-8489: +1. Patch LGTM. [~leftnoteasy] [~eyang] Do you have any

[jira] [Commented] (YARN-8625) Aggregate Resource Allocation for each job is not present in ATS

[ https://issues.apache.org/jira/browse/YARN-8625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745285#comment-16745285 ] Kuhu Shukla commented on YARN-8625: --- Thank you for the patch and the report. Minor checkstyle needs

[jira] [Commented] (YARN-9202) RM does not track nodes that are in the include list and never register

[ https://issues.apache.org/jira/browse/YARN-9202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745268#comment-16745268 ] Kuhu Shukla commented on YARN-9202: --- The test fails with and without the patch and YARN-8494 tracks

[jira] [Updated] (YARN-9205) When using custom resource type, application will fail to run due to the CapacityScheduler throws InvalidResourceRequestException(GREATER_THEN_MAX_ALLOCATION)

[ https://issues.apache.org/jira/browse/YARN-9205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated YARN-9205: --- Attachment: YARN-9205-trunk.001.patch > When using custom resource type, application will fail to run

[jira] [Commented] (YARN-6616) YARN AHS shows submitTime for jobs same as startTime

[ https://issues.apache.org/jira/browse/YARN-6616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745192#comment-16745192 ] Kuhu Shukla commented on YARN-6616: --- Minor comment on {code} @Public @Stable public abstract

[jira] [Commented] (YARN-9204) yarn.scheduler.capacity..accessible-node-labels..capacity can not support absolute resource value

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

[jira] [Updated] (YARN-9205) When using custom resource type, application will fail to run due to the CapacityScheduler throws InvalidResourceRequestException(GREATER_THEN_MAX_ALLOCATION)

[ https://issues.apache.org/jira/browse/YARN-9205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated YARN-9205: --- Description: In a non-secure cluster. Reproduce it as follows: # Set capacity scheduler in

[jira] [Updated] (YARN-9205) When using custom resource type, application will fail to run due to the CapacityScheduler throws InvalidResourceRequestException(GREATER_THEN_MAX_ALLOCATION)

[ https://issues.apache.org/jira/browse/YARN-9205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated YARN-9205: --- Description: In a non-secure cluster. Reproduce it as follows: # Set capacity scheduler in

[jira] [Updated] (YARN-9205) When using custom resource type, application will fail to run due to the CapacityScheduler throws InvalidResourceRequestException(GREATER_THEN_MAX_ALLOCATION)

[ https://issues.apache.org/jira/browse/YARN-9205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated YARN-9205: --- Description: In a non-secure cluster. Reproduce it as follows: # Set capacity scheduler in

[jira] [Updated] (YARN-9205) When using custom resource type, application will fail to run due to the CapacityScheduler throws InvalidResourceRequestException(GREATER_THEN_MAX_ALLOCATION)

[ https://issues.apache.org/jira/browse/YARN-9205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated YARN-9205: --- Description: In a non-secure cluster. Reproduce it as follows: # Set capacity scheduler in

[jira] [Commented] (YARN-9196) Attempt started time zone and Application started time zone is different when OS time zone is modified

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

[jira] [Updated] (YARN-9205) When using custom resource type, application will fail to run due to the CapacityScheduler throws InvalidResourceRequestException(GREATER_THEN_MAX_ALLOCATION)

[ https://issues.apache.org/jira/browse/YARN-9205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated YARN-9205: --- Affects Version/s: 3.3.0 > When using custom resource type, application will fail to run due to the

[jira] [Assigned] (YARN-9205) When using custom resource type, application will fail to run due to the CapacityScheduler throws InvalidResourceRequestException(GREATER_THEN_MAX_ALLOCATION)

[ https://issues.apache.org/jira/browse/YARN-9205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang reassigned YARN-9205: -- Assignee: Zhankun Tang > When using custom resource type, application will fail to run due to

[jira] [Created] (YARN-9205) When using custom resource type, application will fail to run due to the CapacityScheduler throws InvalidResourceRequestException(GREATER_THEN_MAX_ALLOCATION)

Zhankun Tang created YARN-9205: -- Summary: When using custom resource type, application will fail to run due to the CapacityScheduler throws InvalidResourceRequestException(GREATER_THEN_MAX_ALLOCATION) Key: YARN-9205

[jira] [Comment Edited] (YARN-9204) yarn.scheduler.capacity..accessible-node-labels..capacity can not support absolute resource value

[ https://issues.apache.org/jira/browse/YARN-9204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745025#comment-16745025 ] Jiandan Yang edited comment on YARN-9204 at 1/17/19 1:12 PM: -- I apply patch

[jira] [Commented] (YARN-9204) yarn.scheduler.capacity..accessible-node-labels..capacity can not support absolute resource value

[ https://issues.apache.org/jira/browse/YARN-9204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745025#comment-16745025 ] Jiandan Yang commented on YARN-9204: - I apply patch in my test env and RM can start normally.

[jira] [Updated] (YARN-9204) yarn.scheduler.capacity..accessible-node-labels..capacity can not support absolute resource value

[ https://issues.apache.org/jira/browse/YARN-9204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiandan Yang updated YARN-9204: Attachment: YARN-9204.001.patch > > yarn.scheduler.capacity..accessible-node-labels..capacity >

[jira] [Created] (YARN-9204) yarn.scheduler.capacity..accessible-node-labels..capacity can not support absolute resource value

Jiandan Yang created YARN-9204: --- Summary: yarn.scheduler.capacity..accessible-node-labels..capacity can not support absolute resource value Key: YARN-9204 URL: https://issues.apache.org/jira/browse/YARN-9204

[jira] [Commented] (YARN-9191) Add cli option in DS to support enforceExecutionType in resource requests.

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

[jira] [Commented] (YARN-7976) [atsv2 read acls] REST API to list domain/domains

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

[jira] [Commented] (YARN-5336) Limit the flow name size & consider cleanup for hex chars

[ https://issues.apache.org/jira/browse/YARN-5336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744973#comment-16744973 ] Sushil Ks commented on YARN-5336: - Hi [~vrushalic], I have resolved your comments in the new patch. Kindly

[jira] [Updated] (YARN-9191) Add cli option in DS to support enforceExecutionType in resource requests.

[ https://issues.apache.org/jira/browse/YARN-9191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Modi updated YARN-9191: Attachment: YARN-9191.002.patch > Add cli option in DS to support enforceExecutionType in resource

[jira] [Commented] (YARN-5336) Limit the flow name size & consider cleanup for hex chars

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

[jira] [Updated] (YARN-5336) Limit the flow name size & consider cleanup for hex chars

[ https://issues.apache.org/jira/browse/YARN-5336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sushil Ks updated YARN-5336: Attachment: (was: YARN-5336.002.patch) > Limit the flow name size & consider cleanup for hex chars >

[jira] [Updated] (YARN-5336) Limit the flow name size & consider cleanup for hex chars

[ https://issues.apache.org/jira/browse/YARN-5336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sushil Ks updated YARN-5336: Attachment: YARN-5336.002.patch > Limit the flow name size & consider cleanup for hex chars >