[jira] [Commented] (YARN-9693) When AMRMProxyService is enabled RMCommunicator will register with failure

[ https://issues.apache.org/jira/browse/YARN-9693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16986819#comment-16986819 ] panlijie commented on YARN-9693: [~cane] thank you , I will try run this patch > When AMRMProxyService is

[jira] [Commented] (YARN-10010) NM upload log cost too much time

[ https://issues.apache.org/jira/browse/YARN-10010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16986740#comment-16986740 ] Wilfred Spiegelenburg commented on YARN-10010: -- The thread pool size is configurable via

[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] [Updated] (YARN-10011) Catch all exception during init app in LogAggregationService

[ https://issues.apache.org/jira/browse/YARN-10011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhoukang updated YARN-10011: Component/s: nodemanager > Catch all exception during init app in LogAggregationService >

[jira] [Created] (YARN-10011) Catch all exception during init app in LogAggregationService

zhoukang created YARN-10011: --- Summary: Catch all exception during init app in LogAggregationService Key: YARN-10011 URL: https://issues.apache.org/jira/browse/YARN-10011 Project: Hadoop YARN

[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) 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] [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] [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-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=16987236#comment-16987236 ] Jonathan Hung commented on YARN-8292: - [^YARN-8292.branch-2.010.patch] looks fine to me, Ive kicked

[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-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=16987121#comment-16987121 ] Hadoop QA commented on YARN-10009: -- | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote || Subsystem

[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=16987270#comment-16987270 ] Jonathan Hung commented on YARN-9992: - Hmm, not sure how I missed this before, I think it's related to 

[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=16987304#comment-16987304 ] Jonathan Hung commented on YARN-9205: - attached [^YARN-9205-branch-2.001.patch] which contains trivial

[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 ] Jonathan Hung updated YARN-9205: Fix Version/s: 2.11.0 2.10.1 > When using custom resource type, application will

[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=16987319#comment-16987319 ] Hadoop QA commented on YARN-8292: - | (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 ] Jonathan Hung updated YARN-9205: Attachment: YARN-9205-branch-2.001.patch > When using custom resource type, application will fail

[jira] [Created] (YARN-10012) Guaranteed and max capacity queue metrics for custom resources

Jonathan Hung created YARN-10012: Summary: Guaranteed and max capacity queue metrics for custom resources Key: YARN-10012 URL: https://issues.apache.org/jira/browse/YARN-10012 Project: Hadoop YARN

[jira] [Resolved] (YARN-9958) Remove the invalid lock in ContainerExecutor

[ https://issues.apache.org/jira/browse/YARN-9958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka resolved YARN-9958. - Fix Version/s: 3.3.0 Hadoop Flags: Reviewed Resolution: Fixed Committed to trunk.

[jira] [Commented] (YARN-9958) Remove the invalid lock in ContainerExecutor

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