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

[ https://issues.apache.org/jira/browse/YARN-10010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhoukang updated YARN-10010: Attachment: (was: 选区_002.png) > NM upload log cost too much time > >

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

[ https://issues.apache.org/jira/browse/YARN-10010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhoukang updated YARN-10010: Description: Since thread pool size of log service is 100. Some times the log uploading service will delay

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

zhoukang created YARN-10010: --- Summary: NM upload log cost too much time Key: YARN-10010 URL: https://issues.apache.org/jira/browse/YARN-10010 Project: Hadoop YARN Issue Type: Improvement

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

[ https://issues.apache.org/jira/browse/YARN-10010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhoukang updated YARN-10010: Attachment: notfound.png > NM upload log cost too much time > > >

[jira] [Commented] (YARN-8364) NM aggregation thread should be able to exempt pool

[ https://issues.apache.org/jira/browse/YARN-8364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16986613#comment-16986613 ] zhoukang commented on YARN-8364: I will work on this > NM aggregation thread should be able to exempt

[jira] [Commented] (YARN-9985) Unsupported "transitionToObserver" option displaying for rmadmin command

[ https://issues.apache.org/jira/browse/YARN-9985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16986506#comment-16986506 ] Akira Ajisaka commented on YARN-9985: - Thanks [~ayushtkn] for providing the patch. I'm thinking it

[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=16986499#comment-16986499 ] Hadoop QA commented on YARN-10009: -- | (x) *{color:red}-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=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-9561) Add C changes for the new RuncContainerRuntime

[ https://issues.apache.org/jira/browse/YARN-9561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16986353#comment-16986353 ] Eric Badger commented on YARN-9561: --- [~shaneku...@gmail.com], [~eyang], hope the holidays have treated

[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] [Commented] (YARN-9985) Unsupported "transitionToObserver" option displaying for rmadmin command

[ https://issues.apache.org/jira/browse/YARN-9985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16986089#comment-16986089 ] Ayush Saxena commented on YARN-9985: [~aajisaka] [~tasanuma] can you help review. > Unsupported

[jira] [Commented] (YARN-5259) Add two metrics at FSOpDurations for doing container assign and completed Performance statistical analysis

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

[jira] [Updated] (YARN-5259) Add two metrics at FSOpDurations for doing container assign and completed Performance statistical analysis

[ https://issues.apache.org/jira/browse/YARN-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shen Yinjie updated YARN-5259: -- Attachment: YARN-5259_5.patch > Add two metrics at FSOpDurations for doing container assign and