[jira] [Assigned] (YARN-10033) TestProportionalCapacityPreemptionPolicy not initializing vcores for effective max resources

[ https://issues.apache.org/jira/browse/YARN-10033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne reassigned YARN-10033: - Assignee: Eric Payne > TestProportionalCapacityPreemptionPolicy not initializing vcores for >

[jira] [Created] (YARN-10033) TestProportionalCapacityPreemptionPolicy not initializing vcores for effective max resources

Eric Payne created YARN-10033: - Summary: TestProportionalCapacityPreemptionPolicy not initializing vcores for effective max resources Key: YARN-10033 URL: https://issues.apache.org/jira/browse/YARN-10033

[jira] [Commented] (YARN-8292) Fix the dominant resource preemption cannot happen when some of the resource vector becomes negative

[ https://issues.apache.org/jira/browse/YARN-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16994856#comment-16994856 ] Eric Payne commented on YARN-8292: -- Failure of TestProportionalCapacityPreemptionPolicy seems to be

[jira] [Commented] (YARN-9894) CapacitySchedulerPerf test for measuring hundreds of apps in a large number of queues.

[ https://issues.apache.org/jira/browse/YARN-9894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16993925#comment-16993925 ] Eric Payne commented on YARN-9894: -- Thanks a lot, [~jhung] for your review comments. Sorry for the long

[jira] [Updated] (YARN-9894) CapacitySchedulerPerf test for measuring hundreds of apps in a large number of queues.

[ https://issues.apache.org/jira/browse/YARN-9894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-9894: - Attachment: YARN-9894.002.patch > CapacitySchedulerPerf test for measuring hundreds of apps in a large

[jira] [Commented] (YARN-10009) In Capacity Scheduler, DRC can treat minimum user limit percent as a max when custom resource is defined

[ https://issues.apache.org/jira/browse/YARN-10009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16993913#comment-16993913 ] Eric Payne commented on YARN-10009: --- [~leftnoteasy], just a gentle reminder, asking you to take another

[jira] [Commented] (YARN-10009) In Capacity Scheduler, DRC can treat minimum user limit percent as a max when custom resource is defined

[ https://issues.apache.org/jira/browse/YARN-10009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16990202#comment-16990202 ] Eric Payne commented on YARN-10009: --- [~leftnoteasy], thanks for looking at this. bq. is the failure

[jira] [Updated] (YARN-10009) In Capacity Scheduler, DRC can treat minimum user limit percent as a max when custom resource is defined

[ https://issues.apache.org/jira/browse/YARN-10009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-10009: -- Attachment: YARN-10009.branch-2.10.003.patch > In Capacity Scheduler, DRC can treat minimum user limit

[jira] [Commented] (YARN-10009) In Capacity Scheduler, DRC can treat minimum user limit percent as a max when custom resource is defined

[ https://issues.apache.org/jira/browse/YARN-10009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16990024#comment-16990024 ] Eric Payne commented on YARN-10009: --- Upmerged and attached patch version 003. > In Capacity Scheduler,

[jira] [Updated] (YARN-10009) In Capacity Scheduler, DRC can treat minimum user limit percent as a max when custom resource is defined

[ https://issues.apache.org/jira/browse/YARN-10009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-10009: -- Attachment: YARN-10009.003.patch > In Capacity Scheduler, DRC can treat minimum user limit percent as

[jira] [Commented] (YARN-10009) In Capacity Scheduler, DRC can treat minimum user limit percent as a max when custom resource is defined

[ https://issues.apache.org/jira/browse/YARN-10009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16989002#comment-16989002 ] Eric Payne commented on YARN-10009: --- Thank you very much for the review, [~leftnoteasy]. I uploaded a

[jira] [Updated] (YARN-10009) In Capacity Scheduler, DRC can treat minimum user limit percent as a max when custom resource is defined

[ https://issues.apache.org/jira/browse/YARN-10009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-10009: -- Attachment: YARN-10009.002.patch > In Capacity Scheduler, DRC can treat minimum user limit percent as

[jira] [Commented] (YARN-9992) Max allocation per queue is zero for custom resource types on RM startup

[ https://issues.apache.org/jira/browse/YARN-9992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16988937#comment-16988937 ] Eric Payne commented on YARN-9992: -- Thanks [~jhung] , I verified that backporting YARN-9205 fixed the

[jira] [Comment Edited] (YARN-10009) In Capacity Scheduler, DRC can treat minimum user limit percent as a max when custom resource is defined

[ https://issues.apache.org/jira/browse/YARN-10009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16986411#comment-16986411 ] Eric Payne edited comment on YARN-10009 at 12/4/19 6:12 PM: The root cause is

[jira] [Commented] (YARN-8292) Fix the dominant resource preemption cannot happen when some of the resource vector becomes negative

[ https://issues.apache.org/jira/browse/YARN-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16987222#comment-16987222 ] Eric Payne commented on YARN-8292: -- I would like to get this back to branch-2.10. [~sunilg], [~jhung],

[jira] [Commented] (YARN-10009) In Capacity Scheduler, DRC can treat minimum user limit percent as a max when custom resource is defined

[ https://issues.apache.org/jira/browse/YARN-10009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16987181#comment-16987181 ] Eric Payne commented on YARN-10009: --- [~sunilg], [~jhung], [~leftnoteasy], could I please request that

[jira] [Commented] (YARN-9992) Max allocation per queue is zero for custom resource types on RM startup

[ https://issues.apache.org/jira/browse/YARN-9992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16987105#comment-16987105 ] Eric Payne commented on YARN-9992: -- The code changes look fine, but I'm still trying to understand what

[jira] [Updated] (YARN-10009) In Capacity Scheduler, DRC can treat minimum user limit percent as a max when custom resource is defined

[ https://issues.apache.org/jira/browse/YARN-10009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-10009: -- Summary: In Capacity Scheduler, DRC can treat minimum user limit percent as a max when custom resource

[jira] [Updated] (YARN-10009) In Capacity Scheduler, DRF can treat minimum user limit percent as a max when custom resource is defined

[ https://issues.apache.org/jira/browse/YARN-10009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-10009: -- Attachment: YARN-10009.001.patch > In Capacity Scheduler, DRF can treat minimum user limit percent as

[jira] [Updated] (YARN-10009) In Capacity Scheduler, DRF can treat minimum user limit percent as a max when custom resource is defined

[ https://issues.apache.org/jira/browse/YARN-10009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-10009: -- Summary: In Capacity Scheduler, DRF can treat minimum user limit percent as a max when custom resource

[jira] [Updated] (YARN-10009) DRF can treat minimum user limit percent as a max when custom resource is defined

[ https://issues.apache.org/jira/browse/YARN-10009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-10009: -- Component/s: capacity scheduler > DRF can treat minimum user limit percent as a max when custom

[jira] [Commented] (YARN-9992) Max allocation per queue is zero for custom resource types on RM startup

[ https://issues.apache.org/jira/browse/YARN-9992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16986454#comment-16986454 ] Eric Payne commented on YARN-9992: -- [~jhung], it looks like this is only a problem on branch-2 and

[jira] [Updated] (YARN-10009) DRF can treat minimum user limit percent as a max when custom resource is defined

[ https://issues.apache.org/jira/browse/YARN-10009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-10009: -- Description: | |Memory|Vcores|res_1| |Queue1 Totals|20GB|100|80| |Resources requested by App1 in

[jira] [Updated] (YARN-10009) DRF can treat minimum user limit percent as a max when custom resource is defined

[ https://issues.apache.org/jira/browse/YARN-10009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-10009: -- Attachment: YARN-10009.UT.patch > DRF can treat minimum user limit percent as a max when custom

[jira] [Commented] (YARN-10009) DRF can treat minimum user limit percent as a max when custom resource is defined

[ https://issues.apache.org/jira/browse/YARN-10009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16986411#comment-16986411 ] Eric Payne commented on YARN-10009: --- The root cause is here: {code:UsersManager#computeUserLimit}

[jira] [Updated] (YARN-10009) DRF can treat minimum user limit percent as a max when custom resource is defined

[ https://issues.apache.org/jira/browse/YARN-10009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-10009: -- Attachment: (was: YARN-10009.POC.patch) > DRF can treat minimum user limit percent as a max when

[jira] [Updated] (YARN-10009) DRF can treat minimum user limit percent as a max when custom resource is defined

[ https://issues.apache.org/jira/browse/YARN-10009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-10009: -- Attachment: YARN-10009.POC.patch > DRF can treat minimum user limit percent as a max when custom

[jira] [Assigned] (YARN-10009) DRF can treat minimum user limit percent as a max when custom resource is defined

[ https://issues.apache.org/jira/browse/YARN-10009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne reassigned YARN-10009: - Assignee: Eric Payne > DRF can treat minimum user limit percent as a max when custom resource

[jira] [Created] (YARN-10009) DRF can treat minimum user limit percent as a max when custom resource is defined

Eric Payne created YARN-10009: - Summary: DRF can treat minimum user limit percent as a max when custom resource is defined Key: YARN-10009 URL: https://issues.apache.org/jira/browse/YARN-10009 Project:

[jira] [Commented] (YARN-9992) Max allocation per queue is zero for custom resource types on RM startup

[ https://issues.apache.org/jira/browse/YARN-9992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16986312#comment-16986312 ] Eric Payne commented on YARN-9992: -- Thanks [~jhung] for reporting this issue and putting up a patch. I

[jira] [Updated] (YARN-9915) Fix FindBug issue in QueueMetrics

[ https://issues.apache.org/jira/browse/YARN-9915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-9915: - Fix Version/s: 2.11.0 2.10.1 > Fix FindBug issue in QueueMetrics >

[jira] [Updated] (YARN-9773) Add QueueMetrics for Custom Resources

[ https://issues.apache.org/jira/browse/YARN-9773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-9773: - Fix Version/s: 2.11.0 2.10.1 > Add QueueMetrics for Custom Resources >

[jira] [Updated] (YARN-8292) Fix the dominant resource preemption cannot happen when some of the resource vector becomes negative

[ https://issues.apache.org/jira/browse/YARN-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-8292: - Target Version/s: 3.1.1, 3.2.0, 2.10.0, 2.11.0 (was: 3.2.0, 3.1.1, 2.11.0) > Fix the dominant resource

[jira] [Updated] (YARN-8202) DefaultAMSProcessor should properly check units of requested custom resource types against minimum/maximum allocation

[ https://issues.apache.org/jira/browse/YARN-8202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-8202: - Fix Version/s: 2.10.1 > DefaultAMSProcessor should properly check units of requested custom resource >

[jira] [Updated] (YARN-7541) Node updates don't update the maximum cluster capability for resources other than CPU and memory

[ https://issues.apache.org/jira/browse/YARN-7541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-7541: - Fix Version/s: 2.10.1 > Node updates don't update the maximum cluster capability for resources other >

[jira] [Updated] (YARN-7739) DefaultAMSProcessor should properly check customized resource types against minimum/maximum allocation

[ https://issues.apache.org/jira/browse/YARN-7739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-7739: - Fix Version/s: 2.10.1 > DefaultAMSProcessor should properly check customized resource types against >

[jira] [Updated] (YARN-8842) Expose metrics for custom resource types in QueueMetrics

[ https://issues.apache.org/jira/browse/YARN-8842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-8842: - Fix Version/s: 2.11.0 > Expose metrics for custom resource types in QueueMetrics >

[jira] [Commented] (YARN-8842) Expose metrics for custom resource types in QueueMetrics

[ https://issues.apache.org/jira/browse/YARN-8842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16979573#comment-16979573 ] Eric Payne commented on YARN-8842: -- Thanks [~jhung] and [~snemeth] for all of your work on this JIRA. I

[jira] [Commented] (YARN-8842) Expose metrics for custom resource types in QueueMetrics

[ https://issues.apache.org/jira/browse/YARN-8842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16979457#comment-16979457 ] Eric Payne commented on YARN-8842: -- Thanks for the patch, [~jhung]. +1 I will run some more tests and

[jira] [Commented] (YARN-7411) Inter-Queue preemption's computeFixpointAllocation need to handle absolute resources while computing normalizedGuarantee

[ https://issues.apache.org/jira/browse/YARN-7411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16978684#comment-16978684 ] Eric Payne commented on YARN-7411: -- I backported the changes in this JIRA to branch-2 and branch-2.10,

[jira] [Updated] (YARN-7411) Inter-Queue preemption's computeFixpointAllocation need to handle absolute resources while computing normalizedGuarantee

[ https://issues.apache.org/jira/browse/YARN-7411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-7411: - Fix Version/s: 2.11.0 2.10.1 > Inter-Queue preemption's computeFixpointAllocation need

[jira] [Commented] (YARN-9975) Support proxy acl user for CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-9975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16976796#comment-16976796 ] Eric Payne commented on YARN-9975: -- [~cane], does this JIRA have the same requirements outlined in

[jira] [Commented] (YARN-7411) Inter-Queue preemption's computeFixpointAllocation need to handle absolute resources while computing normalizedGuarantee

[ https://issues.apache.org/jira/browse/YARN-7411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16976574#comment-16976574 ] Eric Payne commented on YARN-7411: -- [~sunilg] and [~leftnoteasy], Rather than complicate this by

[jira] [Commented] (YARN-7411) Inter-Queue preemption's computeFixpointAllocation need to handle absolute resources while computing normalizedGuarantee

[ https://issues.apache.org/jira/browse/YARN-7411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16975442#comment-16975442 ] Eric Payne commented on YARN-7411: -- [~sunilg] and [~leftnoteasy]. I backported this JIRA to branch-2 but

[jira] [Updated] (YARN-7411) Inter-Queue preemption's computeFixpointAllocation need to handle absolute resources while computing normalizedGuarantee

[ https://issues.apache.org/jira/browse/YARN-7411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-7411: - Fix Version/s: (was: 2.11.0) (was: 2.10.1) > Inter-Queue preemption's

[jira] [Updated] (YARN-8292) Fix the dominant resource preemption cannot happen when some of the resource vector becomes negative

[ https://issues.apache.org/jira/browse/YARN-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-8292: - Attachment: YARN-8292.branch-2.010.patch > Fix the dominant resource preemption cannot happen when some

[jira] [Updated] (YARN-8292) Fix the dominant resource preemption cannot happen when some of the resource vector becomes negative

[ https://issues.apache.org/jira/browse/YARN-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-8292: - Attachment: (was: YARN-8292.branch-2.010.patcy) > Fix the dominant resource preemption cannot happen

[jira] [Updated] (YARN-8292) Fix the dominant resource preemption cannot happen when some of the resource vector becomes negative

[ https://issues.apache.org/jira/browse/YARN-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-8292: - Attachment: YARN-8292.branch-2.010.patcy > Fix the dominant resource preemption cannot happen when some

[jira] [Updated] (YARN-8292) Fix the dominant resource preemption cannot happen when some of the resource vector becomes negative

[ https://issues.apache.org/jira/browse/YARN-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-8292: - Attachment: (was: 2.8.debug) > Fix the dominant resource preemption cannot happen when some of the

[jira] [Updated] (YARN-8292) Fix the dominant resource preemption cannot happen when some of the resource vector becomes negative

[ https://issues.apache.org/jira/browse/YARN-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-8292: - Attachment: 2.8.debug > Fix the dominant resource preemption cannot happen when some of the resource >

[jira] [Commented] (YARN-7411) Inter-Queue preemption's computeFixpointAllocation need to handle absolute resources while computing normalizedGuarantee

[ https://issues.apache.org/jira/browse/YARN-7411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16975275#comment-16975275 ] Eric Payne commented on YARN-7411: -- This backported cleanly to branch-2 and branch-2.10. I built and ran

[jira] [Updated] (YARN-7411) Inter-Queue preemption's computeFixpointAllocation need to handle absolute resources while computing normalizedGuarantee

[ https://issues.apache.org/jira/browse/YARN-7411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-7411: - Fix Version/s: 2.11.0 2.10.1 > Inter-Queue preemption's computeFixpointAllocation need

[jira] [Commented] (YARN-8179) Preemption does not happen due to natural_termination_factor when DRF is used

[ https://issues.apache.org/jira/browse/YARN-8179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16975264#comment-16975264 ] Eric Payne commented on YARN-8179: -- I would like to backport this to 2.10 so that preemption works

[jira] [Commented] (YARN-7411) Inter-Queue preemption's computeFixpointAllocation need to handle absolute resources while computing normalizedGuarantee

[ https://issues.apache.org/jira/browse/YARN-7411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16975263#comment-16975263 ] Eric Payne commented on YARN-7411: -- I would like to backport this to 2.10 so that preemption works

[jira] [Commented] (YARN-8842) Expose metrics for custom resource types in QueueMetrics

[ https://issues.apache.org/jira/browse/YARN-8842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16975156#comment-16975156 ] Eric Payne commented on YARN-8842: -- Wow, thanks a lot, [~jhung]! I'll hopefully be able to get to the

[jira] [Commented] (YARN-9930) Support max running app logic for CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-9930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970417#comment-16970417 ] Eric Payne commented on YARN-9930: -- The Max Apps Per User Setting exists in CS, but it's a calculated

[jira] [Commented] (YARN-8292) Fix the dominant resource preemption cannot happen when some of the resource vector becomes negative

[ https://issues.apache.org/jira/browse/YARN-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16968732#comment-16968732 ] Eric Payne commented on YARN-8292: -- It looks like the extended resource functionality for preemption unit

[jira] [Commented] (YARN-8292) Fix the dominant resource preemption cannot happen when some of the resource vector becomes negative

[ https://issues.apache.org/jira/browse/YARN-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16968656#comment-16968656 ] Eric Payne commented on YARN-8292: -- I backported this to branch-2 and attached

[jira] [Updated] (YARN-8292) Fix the dominant resource preemption cannot happen when some of the resource vector becomes negative

[ https://issues.apache.org/jira/browse/YARN-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-8292: - Attachment: YARN-8292.branch-2.009.patch > Fix the dominant resource preemption cannot happen when some

[jira] [Commented] (YARN-9930) Support max running app logic for CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-9930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16967930#comment-16967930 ] Eric Payne commented on YARN-9930: -- bq. When we migrate from FS to CS, this difference will make users be

[jira] [Reopened] (YARN-8292) Fix the dominant resource preemption cannot happen when some of the resource vector becomes negative

[ https://issues.apache.org/jira/browse/YARN-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne reopened YARN-8292: -- Sorry for reopening, but this issue also exists in branch-2 and branch-2.10 (see the VOTE discussion

[jira] [Commented] (YARN-8004) Add unit tests for inter queue preemption for dominant resource calculator

[ https://issues.apache.org/jira/browse/YARN-8004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16967660#comment-16967660 ] Eric Payne commented on YARN-8004: -- Backport completed to branch-2 and branch-2.10. > Add unit tests for

[jira] [Updated] (YARN-8004) Add unit tests for inter queue preemption for dominant resource calculator

[ https://issues.apache.org/jira/browse/YARN-8004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-8004: - Fix Version/s: 2.11.0 2.10.1 > Add unit tests for inter queue preemption for dominant

[jira] [Comment Edited] (YARN-8004) Add unit tests for inter queue preemption for dominant resource calculator

[ https://issues.apache.org/jira/browse/YARN-8004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16967606#comment-16967606 ] Eric Payne edited comment on YARN-8004 at 11/5/19 4:16 PM: --- {quote} bq. could i

[jira] [Commented] (YARN-8004) Add unit tests for inter queue preemption for dominant resource calculator

[ https://issues.apache.org/jira/browse/YARN-8004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16967606#comment-16967606 ] Eric Payne commented on YARN-8004: -- {quote} bq. could i backport this to branch-2.9/2.8 as well? Sunil G,

[jira] [Commented] (YARN-9930) Support max running app logic for CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-9930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16966951#comment-16966951 ] Eric Payne commented on YARN-9930: -- bq. Which i want to do in this patch is that pending application but

[jira] [Commented] (YARN-9931) Support run script before kill container

[ https://issues.apache.org/jira/browse/YARN-9931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16966934#comment-16966934 ] Eric Payne commented on YARN-9931: -- [~cane], I'm a little reluctant to add features into the YARN

[jira] [Commented] (YARN-9894) CapacitySchedulerPerf test for measuring hundreds of apps in a large number of queues.

[ https://issues.apache.org/jira/browse/YARN-9894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16966841#comment-16966841 ] Eric Payne commented on YARN-9894: -- [~jhung], [~sunil.gov...@gmail.com], [~leftnoteasy] It would be nice

[jira] [Comment Edited] (YARN-9931) Support run script before kill container

[ https://issues.apache.org/jira/browse/YARN-9931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16962316#comment-16962316 ] Eric Payne edited comment on YARN-9931 at 10/29/19 6:48 PM: [~cane] YARN

[jira] [Commented] (YARN-9931) Support run script before kill container

[ https://issues.apache.org/jira/browse/YARN-9931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16962316#comment-16962316 ] Eric Payne commented on YARN-9931: -- YARN allows the owner of the application (or a cluster admin) to dump

[jira] [Commented] (YARN-9927) RM multi-thread event processing mechanism

[ https://issues.apache.org/jira/browse/YARN-9927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16962135#comment-16962135 ] Eric Payne commented on YARN-9927: -- Thank you [~hcarrot] for bringing this up and for your work in making

[jira] [Commented] (YARN-9915) Fix FindBug issue in QueueMetrics

[ https://issues.apache.org/jira/browse/YARN-9915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956419#comment-16956419 ] Eric Payne commented on YARN-9915: -- Will also backport to 3.2 and 3.1. > Fix FindBug issue in

[jira] [Commented] (YARN-9915) Fix FindBug issue in QueueMetrics

[ https://issues.apache.org/jira/browse/YARN-9915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956415#comment-16956415 ] Eric Payne commented on YARN-9915: -- Thanks for the clarificaion [~Prabhu Joseph]. +1 Will commit soon. >

[jira] [Commented] (YARN-9915) Fix FindBug issue in QueueMetrics

[ https://issues.apache.org/jira/browse/YARN-9915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956391#comment-16956391 ] Eric Payne commented on YARN-9915: -- The changes look correct. The confusing thing is the the [findbugs

[jira] [Commented] (YARN-9915) Fix FindBug issue in QueueMetrics

[ https://issues.apache.org/jira/browse/YARN-9915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956338#comment-16956338 ] Eric Payne commented on YARN-9915: -- Will look this afternoon. > Fix FindBug issue in QueueMetrics >

[jira] [Resolved] (YARN-9773) Add QueueMetrics for Custom Resources

[ https://issues.apache.org/jira/browse/YARN-9773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne resolved YARN-9773. -- Fix Version/s: 3.1.4 3.2.2 3.3.0 Resolution: Fixed Thanks

[jira] [Created] (YARN-9911) Backport YARN-9773 (Add QueueMetrics for Custom Resources) to branch-2 and branch-2.10

Eric Payne created YARN-9911: Summary: Backport YARN-9773 (Add QueueMetrics for Custom Resources) to branch-2 and branch-2.10 Key: YARN-9911 URL: https://issues.apache.org/jira/browse/YARN-9911 Project:

[jira] [Commented] (YARN-9773) Add QueueMetrics for Custom Resources

[ https://issues.apache.org/jira/browse/YARN-9773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16953182#comment-16953182 ] Eric Payne commented on YARN-9773: -- [~maniraj...@gmail.com], I was able to backport YARN-8750 to

[jira] [Commented] (YARN-8842) Expose metrics for custom resource types in QueueMetrics

[ https://issues.apache.org/jira/browse/YARN-8842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16953127#comment-16953127 ] Eric Payne commented on YARN-8842: -- Hi [~snemeth]. I would like this functionality to be backported to

[jira] [Updated] (YARN-8842) Expose metrics for custom resource types in QueueMetrics

[ https://issues.apache.org/jira/browse/YARN-8842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-8842: - Fix Version/s: 3.1.4 3.2.2 > Expose metrics for custom resource types in QueueMetrics

[jira] [Commented] (YARN-8842) Expose metrics for custom resource types in QueueMetrics

[ https://issues.apache.org/jira/browse/YARN-8842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16952342#comment-16952342 ] Eric Payne commented on YARN-8842: -- I backported to branch-3.2 and 3.1, but putting it into branch-2

[jira] [Commented] (YARN-7739) DefaultAMSProcessor should properly check customized resource types against minimum/maximum allocation

[ https://issues.apache.org/jira/browse/YARN-7739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16952254#comment-16952254 ] Eric Payne commented on YARN-7739: -- I would like to backport this to branch-2 unless there are

[jira] [Updated] (YARN-8750) Refactor TestQueueMetrics

[ https://issues.apache.org/jira/browse/YARN-8750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-8750: - Fix Version/s: 3.1.4 3.2.2 2.10.0 > Refactor TestQueueMetrics >

[jira] [Commented] (YARN-8842) Expose metrics for custom resource types in QueueMetrics

[ https://issues.apache.org/jira/browse/YARN-8842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16952016#comment-16952016 ] Eric Payne commented on YARN-8842: -- I'd like to backport this to branch-2 if there are no objections. >

[jira] [Commented] (YARN-8750) Refactor TestQueueMetrics

[ https://issues.apache.org/jira/browse/YARN-8750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16952013#comment-16952013 ] Eric Payne commented on YARN-8750: -- I'd like to backport this to branch-2 if there are no objections. >

[jira] [Commented] (YARN-9773) Add QueueMetrics for Custom Resources

[ https://issues.apache.org/jira/browse/YARN-9773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16951386#comment-16951386 ] Eric Payne commented on YARN-9773: -- Thanks again, [~maniraj...@gmail.com]. The changes look good. I'm

[jira] [Commented] (YARN-9773) Add QueueMetrics for Custom Resources

[ https://issues.apache.org/jira/browse/YARN-9773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16951142#comment-16951142 ] Eric Payne commented on YARN-9773: -- [~maniraj...@gmail.com], Sorry for the long delay. Thanks for the

[jira] [Assigned] (YARN-2127) Move YarnUncaughtExceptionHandler into Hadoop common

[ https://issues.apache.org/jira/browse/YARN-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne reassigned YARN-2127: Assignee: Eric Payne (was: Eric Payne) > Move YarnUncaughtExceptionHandler into Hadoop common >

[jira] [Commented] (YARN-6492) Generate queue metrics for each partition

[ https://issues.apache.org/jira/browse/YARN-6492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16951001#comment-16951001 ] Eric Payne commented on YARN-6492: -- [~gaurav.suman], my understanding is that branch-3.0 has been

[jira] [Updated] (YARN-9894) CapacitySchedulerPerf test for measuring hundreds of apps in a large number of queues.

[ https://issues.apache.org/jira/browse/YARN-9894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-9894: - Attachment: YARN-9894.001.patch > CapacitySchedulerPerf test for measuring hundreds of apps in a large

[jira] [Updated] (YARN-9894) CapacitySchedulerPerf test for measuring hundreds of apps in a large number of queues.

[ https://issues.apache.org/jira/browse/YARN-9894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-9894: - Attachment: YARN-9894.001.patch > CapacitySchedulerPerf test for measuring hundreds of apps in a large

[jira] [Updated] (YARN-9894) CapacitySchedulerPerf test for measuring hundreds of apps in a large number of queues.

[ https://issues.apache.org/jira/browse/YARN-9894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-9894: - Attachment: (was: YARN-9894.001.patch) > CapacitySchedulerPerf test for measuring hundreds of apps in

[jira] [Commented] (YARN-9887) Capacity scheduler: add support for limiting maxRunningApps per user

[ https://issues.apache.org/jira/browse/YARN-9887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949690#comment-16949690 ] Eric Payne commented on YARN-9887: -- The Capacity Scheduler does have a concept of {color:#22}Max

[jira] [Assigned] (YARN-9894) CapacitySchedulerPerf test for measuring hundreds of apps in a large number of queues.

[ https://issues.apache.org/jira/browse/YARN-9894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne reassigned YARN-9894: Assignee: Eric Payne (was: Eric Payne) > CapacitySchedulerPerf test for measuring hundreds of

[jira] [Assigned] (YARN-9894) CapacitySchedulerPerf test for measuring hundreds of apps in a large number of queues.

[ https://issues.apache.org/jira/browse/YARN-9894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne reassigned YARN-9894: Assignee: Eric Payne > CapacitySchedulerPerf test for measuring hundreds of apps in a large number

[jira] [Created] (YARN-9894) CapacitySchedulerPerf test for measuring hundreds of apps in a large number of queues.

Eric Payne created YARN-9894: Summary: CapacitySchedulerPerf test for measuring hundreds of apps in a large number of queues. Key: YARN-9894 URL: https://issues.apache.org/jira/browse/YARN-9894 Project:

[jira] [Commented] (YARN-9882) QueueMetrics not coming in Capacity Scheduler with Node Label Configuration

[ https://issues.apache.org/jira/browse/YARN-9882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949573#comment-16949573 ] Eric Payne commented on YARN-9882: -- [~gaurav.suman], for the sake of legacy, the metrics outside of the

[jira] [Commented] (YARN-7817) Add Resource reference to RM's NodeInfo object so REST API can get non memory/vcore resource usages.

[ https://issues.apache.org/jira/browse/YARN-7817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16934389#comment-16934389 ] Eric Payne commented on YARN-7817: -- I backported YARN-7817 and YARN-7860 to branch-2. > Add Resource

[jira] [Updated] (YARN-7860) Fix UT failure TestRMWebServiceAppsNodelabel#testAppsRunning

[ https://issues.apache.org/jira/browse/YARN-7860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-7860: - Fix Version/s: 2.10.0 > Fix UT failure TestRMWebServiceAppsNodelabel#testAppsRunning >

[jira] [Updated] (YARN-7817) Add Resource reference to RM's NodeInfo object so REST API can get non memory/vcore resource usages.

[ https://issues.apache.org/jira/browse/YARN-7817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-7817: - Fix Version/s: 2.10.0 > Add Resource reference to RM's NodeInfo object so REST API can get non >

<    1   2   3   4   5   6   7   8   9   10   >