[jira] [Commented] (YARN-10707) Support custom resources in ResourceUtilization, and update Node GPU Utilization to use.

[ https://issues.apache.org/jira/browse/YARN-10707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17326452#comment-17326452 ] Qi Zhu commented on YARN-10707: --- Thanks [~ebadger] for very good suggestions. It make sens

[jira] [Commented] (YARN-10723) Change CS nodes page in UI to support custom resource.

[ https://issues.apache.org/jira/browse/YARN-10723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17326227#comment-17326227 ] Qi Zhu commented on YARN-10723: --- Thanks [~ebadger] for commit. > Change CS nodes page in U

[jira] [Commented] (YARN-10723) Change CS nodes page in UI to support custom resource.

[ https://issues.apache.org/jira/browse/YARN-10723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17325526#comment-17325526 ] Qi Zhu commented on YARN-10723: --- [~ebadger] The test error is not related to this, passed l

[jira] [Commented] (YARN-10715) Remove hardcoded resource values (e.g. GPU/FPGA) in code.

[ https://issues.apache.org/jira/browse/YARN-10715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17325442#comment-17325442 ] Qi Zhu commented on YARN-10715: --- Thanks [~ebadger] for reply. It make sense to me. I will

[jira] [Commented] (YARN-10723) Change CS nodes page in UI to support custom resource.

[ https://issues.apache.org/jira/browse/YARN-10723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17325438#comment-17325438 ] Qi Zhu commented on YARN-10723: --- [~ebadger] Sure, i uploaded 005 patch to trigger jenkins.

[jira] [Updated] (YARN-10723) Change CS nodes page in UI to support custom resource.

[ https://issues.apache.org/jira/browse/YARN-10723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-10723: -- Attachment: YARN-10723.005.patch > Change CS nodes page in UI to support custom resource. > ---

[jira] [Comment Edited] (YARN-10743) Add a policy for not aggregating for containers which are killed because exceeding container log size limit.

[ https://issues.apache.org/jira/browse/YARN-10743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17325432#comment-17325432 ] Qi Zhu edited comment on YARN-10743 at 4/20/21, 3:04 AM: - Thanks

[jira] [Comment Edited] (YARN-10743) Add a policy for not aggregating for containers which are killed because exceeding container log size limit.

[ https://issues.apache.org/jira/browse/YARN-10743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17325432#comment-17325432 ] Qi Zhu edited comment on YARN-10743 at 4/20/21, 3:02 AM: - Thanks

[jira] [Commented] (YARN-10743) Add a policy for not aggregating for containers which are killed because exceeding container log size limit.

[ https://issues.apache.org/jira/browse/YARN-10743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17325432#comment-17325432 ] Qi Zhu commented on YARN-10743: --- Thanks [~ebadger] for reply. One case in our cluster : I

[jira] [Updated] (YARN-10743) Add a policy for not aggregating for containers which are killed because exceeding container log size limit.

[ https://issues.apache.org/jira/browse/YARN-10743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-10743: -- Attachment: image-2021-04-20-10-41-01-057.png > Add a policy for not aggregating for containers which are kille

[jira] [Comment Edited] (YARN-10743) Add a policy for not aggregating for containers which are killed because exceeding container log size limit.

[ https://issues.apache.org/jira/browse/YARN-10743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17325109#comment-17325109 ] Qi Zhu edited comment on YARN-10743 at 4/19/21, 3:22 PM: - Thanks

[jira] [Comment Edited] (YARN-10743) Add a policy for not aggregating for containers which are killed because exceeding container log size limit.

[ https://issues.apache.org/jira/browse/YARN-10743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17325109#comment-17325109 ] Qi Zhu edited comment on YARN-10743 at 4/19/21, 3:21 PM: - Thanks

[jira] [Commented] (YARN-10743) Add a policy for not aggregating for containers which are killed because exceeding container log size limit.

[ https://issues.apache.org/jira/browse/YARN-10743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17325109#comment-17325109 ] Qi Zhu commented on YARN-10743: --- Thanks [~Jim_Brennan] for reply. But in our cluster, some

[jira] [Updated] (YARN-10743) Add a policy for not aggregating for containers which are killed because exceeding container log size limit.

[ https://issues.apache.org/jira/browse/YARN-10743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-10743: -- Summary: Add a policy for not aggregating for containers which are killed because exceeding container log size

[jira] [Created] (YARN-10743) Add a policy for not aggregating for container log size limit killed container.

Qi Zhu created YARN-10743: - Summary: Add a policy for not aggregating for container log size limit killed container. Key: YARN-10743 URL: https://issues.apache.org/jira/browse/YARN-10743 Project: Hadoop YARN

[jira] [Commented] (YARN-9869) Create scheduling policy to auto-adjust queue elasticity based on cluster demand

[ https://issues.apache.org/jira/browse/YARN-9869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17324495#comment-17324495 ] Qi Zhu commented on YARN-9869: -- cc [~jhung] Is this going on ? I think it's a very good imp

[jira] [Commented] (YARN-10723) Change CS nodes page in UI to support custom resource.

[ https://issues.apache.org/jira/browse/YARN-10723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17324158#comment-17324158 ] Qi Zhu commented on YARN-10723: --- Thanks a lot [~ebadger] for confirm. > Change CS nodes pa

[jira] [Commented] (YARN-10739) GenericEventHandler.printEventQueueDetails cause RM recovery cost too much time

[ https://issues.apache.org/jira/browse/YARN-10739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17323863#comment-17323863 ] Qi Zhu commented on YARN-10739: --- Trigger the jenkins.  > GenericEventHandler.printEventQue

[jira] [Comment Edited] (YARN-10739) GenericEventHandler.printEventQueueDetails cause RM recovery cost too much time

[ https://issues.apache.org/jira/browse/YARN-10739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17323833#comment-17323833 ] Qi Zhu edited comment on YARN-10739 at 4/16/21, 1:58 PM: - [~zhanq

[jira] [Commented] (YARN-10739) GenericEventHandler.printEventQueueDetails cause RM recovery cost too much time

[ https://issues.apache.org/jira/browse/YARN-10739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17323833#comment-17323833 ] Qi Zhu commented on YARN-10739: --- [~zhanqi.cai] I don't think wait 30s is a good choice aft

[jira] [Updated] (YARN-10739) GenericEventHandler.printEventQueueDetails cause RM recovery cost too much time

[ https://issues.apache.org/jira/browse/YARN-10739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-10739: -- Attachment: YARN-10739.003.patch > GenericEventHandler.printEventQueueDetails cause RM recovery cost too much

[jira] [Assigned] (YARN-10739) GenericEventHandler.printEventQueueDetails cause RM recovery cost too much time

[ https://issues.apache.org/jira/browse/YARN-10739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu reassigned YARN-10739: - Assignee: Qi Zhu > GenericEventHandler.printEventQueueDetails cause RM recovery cost too much > time >

[jira] [Comment Edited] (YARN-10739) GenericEventHandler.printEventQueueDetails cause RM recovery cost too much time

[ https://issues.apache.org/jira/browse/YARN-10739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17323774#comment-17323774 ] Qi Zhu edited comment on YARN-10739 at 4/16/21, 12:37 PM: -- Thank

[jira] [Comment Edited] (YARN-10739) GenericEventHandler.printEventQueueDetails cause RM recovery cost too much time

[ https://issues.apache.org/jira/browse/YARN-10739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17323774#comment-17323774 ] Qi Zhu edited comment on YARN-10739 at 4/16/21, 12:36 PM: -- Thank

[jira] [Comment Edited] (YARN-10739) GenericEventHandler.printEventQueueDetails cause RM recovery cost too much time

[ https://issues.apache.org/jira/browse/YARN-10739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17323774#comment-17323774 ] Qi Zhu edited comment on YARN-10739 at 4/16/21, 12:33 PM: -- Thank

[jira] [Comment Edited] (YARN-10739) GenericEventHandler.printEventQueueDetails cause RM recovery cost too much time

[ https://issues.apache.org/jira/browse/YARN-10739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17323774#comment-17323774 ] Qi Zhu edited comment on YARN-10739 at 4/16/21, 12:26 PM: -- Thank

[jira] [Commented] (YARN-10739) GenericEventHandler.printEventQueueDetails cause RM recovery cost too much time

[ https://issues.apache.org/jira/browse/YARN-10739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17323774#comment-17323774 ] Qi Zhu commented on YARN-10739: --- Thanks [~zhanqi.cai] for reporting this, the patch LGTM ge

[jira] [Commented] (YARN-10738) When multi thread scheduling with multi node, we should shuffle with a gap to prevent hot accessing nodes.

[ https://issues.apache.org/jira/browse/YARN-10738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17322560#comment-17322560 ] Qi Zhu commented on YARN-10738: --- [~Jim_Brennan] Could you help review this, when you are f

[jira] [Commented] (YARN-10738) When multi thread scheduling with multi node, we should shuffle with a gap to prevent hot accessing nodes.

[ https://issues.apache.org/jira/browse/YARN-10738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17322004#comment-17322004 ] Qi Zhu commented on YARN-10738: --- I have changed to *MultiNodeLookupPolicy * implementation

[jira] [Updated] (YARN-10738) When multi thread scheduling with multi node, we should shuffle to prevent hot accessing nodes.

[ https://issues.apache.org/jira/browse/YARN-10738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-10738: -- Target Version/s: 3.4.0 > When multi thread scheduling with multi node, we should shuffle to prevent > hot acc

[jira] [Updated] (YARN-10738) When multi thread scheduling with multi node, we should shuffle with a gap to prevent hot accessing nodes.

[ https://issues.apache.org/jira/browse/YARN-10738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-10738: -- Summary: When multi thread scheduling with multi node, we should shuffle with a gap to prevent hot accessing no

[jira] [Commented] (YARN-10738) When multi thread scheduling with multi node, we should shuffle to prevent hot accessing nodes.

[ https://issues.apache.org/jira/browse/YARN-10738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321936#comment-17321936 ] Qi Zhu commented on YARN-10738: --- Thanks a lot [~bibinchundatt] for reply. :D I will move i

[jira] [Commented] (YARN-10738) When multi thread scheduling with multi node, we should shuffle to prevent hot accessing nodes.

[ https://issues.apache.org/jira/browse/YARN-10738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321926#comment-17321926 ] Qi Zhu commented on YARN-10738: --- cc [~ztang]  [~snemeth] [~pbacsko] [~gandras] [~ebadger] [

[jira] [Updated] (YARN-10738) When multi thread scheduling with multi node, we should shuffle to prevent hot accessing nodes.

[ https://issues.apache.org/jira/browse/YARN-10738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-10738: -- Description: Now the multi threading scheduling with multi node is not reasonable. In large clusters, it will

[jira] [Updated] (YARN-10738) When multi thread scheduling with multi node, we should shuffle to prevent hot accessing nodes.

[ https://issues.apache.org/jira/browse/YARN-10738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-10738: -- Description: Now the multi threading scheduling with multi node is not reasonable. In large clusters, it will

[jira] [Updated] (YARN-10738) When multi thread scheduling with multi node, we should shuffle to prevent hot accessing nodes.

[ https://issues.apache.org/jira/browse/YARN-10738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-10738: -- Description: Now the multi threading scheduling  > When multi thread scheduling with multi node, we should shuf

[jira] [Created] (YARN-10738) When multi thread scheduling with multi node, we should shuffle to prevent hot accessing nodes.

Qi Zhu created YARN-10738: - Summary: When multi thread scheduling with multi node, we should shuffle to prevent hot accessing nodes. Key: YARN-10738 URL: https://issues.apache.org/jira/browse/YARN-10738 Proje

[jira] [Created] (YARN-10737) Fix typos in CapacityScheduler#schedule.

Qi Zhu created YARN-10737: - Summary: Fix typos in CapacityScheduler#schedule. Key: YARN-10737 URL: https://issues.apache.org/jira/browse/YARN-10737 Project: Hadoop YARN Issue Type: Improvement

[jira] [Commented] (YARN-8418) App local logs could leaked if log aggregation fails to initialize for the app

[ https://issues.apache.org/jira/browse/YARN-8418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17320677#comment-17320677 ] Qi Zhu commented on YARN-8418: -- [~bibinchundatt] [~rohithsharma]  Could you help backport to

[jira] [Commented] (YARN-10734) Log aggregation create dir throw failed to setup application log directory, but the log dir not deleted.

[ https://issues.apache.org/jira/browse/YARN-10734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17320665#comment-17320665 ] Qi Zhu commented on YARN-10734: --- I find it duplicated with YARN-8418 , so i close it now.

[jira] [Resolved] (YARN-10734) Log aggregation create dir throw failed to setup application log directory, but the log dir not deleted.

[ https://issues.apache.org/jira/browse/YARN-10734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu resolved YARN-10734. --- Resolution: Duplicate > Log aggregation create dir throw failed to setup application log directory, > but th

[jira] [Updated] (YARN-10734) Log aggregation create dir throw failed to setup application log directory, but the log dir not deleted.

[ https://issues.apache.org/jira/browse/YARN-10734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-10734: -- Description: As follows log aggregation create dir throw failed to setup application log directory : !image-2

[jira] [Commented] (YARN-10648) NM local logs are not cleared after uploading to hdfs

[ https://issues.apache.org/jira/browse/YARN-10648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17320022#comment-17320022 ] Qi Zhu commented on YARN-10648: --- Thanks [~dmmkr] for good finding. LGTM +1.  [~brahmaredd

[jira] [Comment Edited] (YARN-10734) Log aggregation create dir throw failed to setup application log directory, but the log dir not deleted.

[ https://issues.apache.org/jira/browse/YARN-10734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17320016#comment-17320016 ] Qi Zhu edited comment on YARN-10734 at 4/13/21, 8:14 AM: - cc [~sn

[jira] [Updated] (YARN-10734) Log aggregation create dir throw failed to setup application log directory, but the log dir not deleted.

[ https://issues.apache.org/jira/browse/YARN-10734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-10734: -- Description: As follows log aggregation create dir throw failed to setup application log directory : !image-2

[jira] [Commented] (YARN-10734) Log aggregation create dir throw failed to setup application log directory, but the log dir not deleted.

[ https://issues.apache.org/jira/browse/YARN-10734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17320016#comment-17320016 ] Qi Zhu commented on YARN-10734: --- cc [~pbacsko] [~gandras] [~ebadger] [~epayne]   What's yo

[jira] [Updated] (YARN-10734) Log aggregation create dir throw failed to setup application log directory, but the log dir not deleted.

[ https://issues.apache.org/jira/browse/YARN-10734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-10734: -- Description: As follows log aggregation create dir throw failed to setup application log directory : !image-2

[jira] [Updated] (YARN-10734) Log aggregation create dir throw failed to setup application log directory, but the log dir not deleted.

[ https://issues.apache.org/jira/browse/YARN-10734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-10734: -- Issue Type: Bug (was: Improvement) > Log aggregation create dir throw failed to setup application log director

[jira] [Updated] (YARN-10734) Log aggregation create dir throw failed to setup application log directory, but the log dir not deleted.

[ https://issues.apache.org/jira/browse/YARN-10734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-10734: -- Description: As follows log aggregation create dir throw failed to setup application log directory : !image-2

[jira] [Updated] (YARN-10734) Log aggregation create dir throw failed to setup application log directory, but the log dir not deleted.

[ https://issues.apache.org/jira/browse/YARN-10734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-10734: -- Attachment: image-2021-04-13-15-39-27-446.png > Log aggregation create dir throw failed to setup application lo

[jira] [Updated] (YARN-10734) Log aggregation create dir throw failed to setup application log directory, but the log dir not deleted.

[ https://issues.apache.org/jira/browse/YARN-10734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-10734: -- Description: As follows log aggregation create dir throw failed to setup application log directory : !image-2

[jira] [Updated] (YARN-10734) Log aggregation create dir throw failed to setup application log directory, but the log dir not deleted.

[ https://issues.apache.org/jira/browse/YARN-10734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-10734: -- Description:   !image-2021-04-13-15-34-22-732.png|width=756,height=166! was:!image-2021-04-13-15-34-22-732.

[jira] [Updated] (YARN-10734) Log aggregation create dir throw failed to setup application log directory, but the log dir not deleted.

[ https://issues.apache.org/jira/browse/YARN-10734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-10734: -- Summary: Log aggregation create dir throw failed to setup application log directory, but the log dir not delete

[jira] [Updated] (YARN-10734) Log aggregation create dir throw failed to setup application log directory, but the dir existed.

[ https://issues.apache.org/jira/browse/YARN-10734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-10734: -- Description: !image-2021-04-13-15-34-22-732.png|width=756,height=166! > Log aggregation create dir throw failed

[jira] [Updated] (YARN-10734) Log aggregation create dir throw failed to setup application log directory, but the dir existed.

[ https://issues.apache.org/jira/browse/YARN-10734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-10734: -- Attachment: image-2021-04-13-15-34-22-732.png > Log aggregation create dir throw failed to setup application lo

[jira] [Updated] (YARN-10734) Log aggregation create dir throw failed to setup application log directory, but the dir existed.

[ https://issues.apache.org/jira/browse/YARN-10734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-10734: -- Attachment: image-2021-04-13-15-33-06-387.png > Log aggregation create dir throw failed to setup application lo

[jira] [Created] (YARN-10734) Log aggregation create dir throw failed to setup application log directory, but the dir existed.

Qi Zhu created YARN-10734: - Summary: Log aggregation create dir throw failed to setup application log directory, but the dir existed. Key: YARN-10734 URL: https://issues.apache.org/jira/browse/YARN-10734 Proj

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

[ https://issues.apache.org/jira/browse/YARN-9927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-9927: - Attachment: YARN-9927.004.patch > RM multi-thread event processing mechanism > ---

[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&focusedCommentId=17319898#comment-17319898 ] Qi Zhu commented on YARN-9927: -- Fixed the checkstyle in latest patch. cc [~gandras] [~pbacsk

[jira] [Commented] (YARN-10732) Disallow restarting a queue while it is in DRAINING state on CS reinitialization

[ https://issues.apache.org/jira/browse/YARN-10732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17319516#comment-17319516 ] Qi Zhu commented on YARN-10732: --- Thanks [~gandras] for good finding. The patch LGTM. +1  

[jira] [Commented] (YARN-10503) Support queue capacity in terms of absolute resources with custom resourceType.

[ https://issues.apache.org/jira/browse/YARN-10503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318431#comment-17318431 ] Qi Zhu commented on YARN-10503: --- Thanks [~ebadger] for commit to 3.4 and branch-3.3. > Sup

[jira] [Commented] (YARN-10503) Support queue capacity in terms of absolute resources with custom resourceType.

[ https://issues.apache.org/jira/browse/YARN-10503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17317801#comment-17317801 ] Qi Zhu commented on YARN-10503: --- [~ebadger] The test is not related to branch-3.3 backport

[jira] [Commented] (YARN-10503) Support queue capacity in terms of absolute resources with custom resourceType.

[ https://issues.apache.org/jira/browse/YARN-10503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17317599#comment-17317599 ] Qi Zhu commented on YARN-10503: --- Thanks [~ebadger] for commit. I have updated a patch to  

[jira] [Updated] (YARN-10503) Support queue capacity in terms of absolute resources with custom resourceType.

[ https://issues.apache.org/jira/browse/YARN-10503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-10503: -- Attachment: YARN-10503-branch-3.3.010.patch > Support queue capacity in terms of absolute resources with custom

[jira] [Comment Edited] (YARN-10178) Global Scheduler async thread crash caused by 'Comparison method violates its general contract'

[ https://issues.apache.org/jira/browse/YARN-10178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17297785#comment-17297785 ] Qi Zhu edited comment on YARN-10178 at 4/8/21, 2:23 PM: Thanks [~

[jira] [Updated] (YARN-10728) CS should support ensureRootPrefix in queuePath to consistent with FS.

[ https://issues.apache.org/jira/browse/YARN-10728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-10728: -- Description: {code:java} private static String ensureRootPrefix(String name) { if (!name.startsWith(ROOT_QUEU

[jira] [Commented] (YARN-10637) We should support fs to cs support for auto refresh queues when conf changed, after YARN-10623 finished.

[ https://issues.apache.org/jira/browse/YARN-10637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17316917#comment-17316917 ] Qi Zhu commented on YARN-10637: ---   [~gandras] Could you take a look this when you are free

[jira] [Updated] (YARN-10728) CS should support ensureRootPrefix in queuePath to consistent with FS.

[ https://issues.apache.org/jira/browse/YARN-10728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-10728: -- Summary: CS should support ensureRootPrefix in queuePath to consistent with FS. (was: CS should support ensure

[jira] [Updated] (YARN-10728) CS should support ensureRootPrefix to consistent with FS.

[ https://issues.apache.org/jira/browse/YARN-10728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-10728: -- Description: {code:java} private static String ensureRootPrefix(String name) { if (!name.startsWith(ROOT_QUEU

[jira] [Updated] (YARN-10728) CS should support ensureRootPrefix to consistent with FS.

[ https://issues.apache.org/jira/browse/YARN-10728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-10728: -- Description: {code:java} private static String ensureRootPrefix(String name) { if (!name.startsWith(ROOT_QUEU

[jira] [Created] (YARN-10728) CS should support ensureRootPrefix to consistent with FS.

Qi Zhu created YARN-10728: - Summary: CS should support ensureRootPrefix to consistent with FS. Key: YARN-10728 URL: https://issues.apache.org/jira/browse/YARN-10728 Project: Hadoop YARN Issue Type: I

[jira] [Commented] (YARN-10564) Support Auto Queue Creation template configurations

[ https://issues.apache.org/jira/browse/YARN-10564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17316834#comment-17316834 ] Qi Zhu commented on YARN-10564: --- Thanks [~pbacsko] review and suggestion,  [~gandras] for u

[jira] [Comment Edited] (YARN-10723) Change CS nodes page in UI to support custom resource.

[ https://issues.apache.org/jira/browse/YARN-10723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315382#comment-17315382 ] Qi Zhu edited comment on YARN-10723 at 4/6/21, 9:22 AM: Thanks [~

[jira] [Commented] (YARN-10723) Change CS nodes page in UI to support custom resource.

[ https://issues.apache.org/jira/browse/YARN-10723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315382#comment-17315382 ] Qi Zhu commented on YARN-10723: --- Thanks [~gandras] for very good suggestions. Update it in

[jira] [Updated] (YARN-10723) Change CS nodes page in UI to support custom resource.

[ https://issues.apache.org/jira/browse/YARN-10723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-10723: -- Attachment: YARN-10723.004.patch > Change CS nodes page in UI to support custom resource. > ---

[jira] [Comment Edited] (YARN-10503) Support queue capacity in terms of absolute resources with custom resourceType.

[ https://issues.apache.org/jira/browse/YARN-10503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315349#comment-17315349 ] Qi Zhu edited comment on YARN-10503 at 4/6/21, 8:51 AM: Thanks [~

[jira] [Comment Edited] (YARN-10657) We should make max application per queue to support node label.

[ https://issues.apache.org/jira/browse/YARN-10657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315353#comment-17315353 ] Qi Zhu edited comment on YARN-10657 at 4/6/21, 8:49 AM: Thanks [~

[jira] [Commented] (YARN-10657) We should make max application per queue to support node label.

[ https://issues.apache.org/jira/browse/YARN-10657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315353#comment-17315353 ] Qi Zhu commented on YARN-10657: --- Thanks [~gandras] for review. I agree with you the curren

[jira] [Commented] (YARN-10503) Support queue capacity in terms of absolute resources with custom resourceType.

[ https://issues.apache.org/jira/browse/YARN-10503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315349#comment-17315349 ] Qi Zhu commented on YARN-10503: --- Thanks [~gandras] for review and confirm. And the suggest

[jira] [Updated] (YARN-10503) Support queue capacity in terms of absolute resources with custom resourceType.

[ https://issues.apache.org/jira/browse/YARN-10503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-10503: -- Attachment: YARN-10503.010.patch > Support queue capacity in terms of absolute resources with custom > resourc

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

[ https://issues.apache.org/jira/browse/YARN-9927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-9927: - Attachment: YARN-9927.003.patch > RM multi-thread event processing mechanism > ---

[jira] [Comment Edited] (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&focusedCommentId=17314294#comment-17314294 ] Qi Zhu edited comment on YARN-9927 at 4/3/21, 4:24 PM: --- [~gandras] [

[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&focusedCommentId=17314294#comment-17314294 ] Qi Zhu commented on YARN-9927: -- [~gandras] [~pbacsko]  Updated a patch, each eventType will

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

[ https://issues.apache.org/jira/browse/YARN-9927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-9927: - Attachment: YARN-9927.002.patch > RM multi-thread event processing mechanism > ---

[jira] [Comment Edited] (YARN-10726) Log the size of DelegationTokenRenewer event queue in case of too many pending events

[ https://issues.apache.org/jira/browse/YARN-10726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313243#comment-17313243 ] Qi Zhu edited comment on YARN-10726 at 4/1/21, 3:36 PM: [~pbacsko

[jira] [Commented] (YARN-10726) Log the size of DelegationTokenRenewer event queue in case of too many pending events

[ https://issues.apache.org/jira/browse/YARN-10726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313243#comment-17313243 ] Qi Zhu commented on YARN-10726: --- [~pbacsko] I tested locally just now, it passed. Thanks.

[jira] [Comment Edited] (YARN-10503) Support queue capacity in terms of absolute resources with custom resourceType.

[ https://issues.apache.org/jira/browse/YARN-10503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17312219#comment-17312219 ] Qi Zhu edited comment on YARN-10503 at 4/1/21, 3:10 PM: [~pbacsko

[jira] [Comment Edited] (YARN-10503) Support queue capacity in terms of absolute resources with custom resourceType.

[ https://issues.apache.org/jira/browse/YARN-10503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17312219#comment-17312219 ] Qi Zhu edited comment on YARN-10503 at 4/1/21, 3:05 PM: [~pbacsko

[jira] [Commented] (YARN-10693) Add document for YARN-10623 auto refresh queue conf in cs.

[ https://issues.apache.org/jira/browse/YARN-10693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313199#comment-17313199 ] Qi Zhu commented on YARN-10693: --- [~pbacsko] This is the corresponding document. :D > Add

[jira] [Commented] (YARN-10637) We should support fs to cs support for auto refresh queues when conf changed, after YARN-10623 finished.

[ https://issues.apache.org/jira/browse/YARN-10637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313196#comment-17313196 ] Qi Zhu commented on YARN-10637: --- Thanks [~pbacsko] for review. Actually fs always enabled

[jira] [Commented] (YARN-10726) Log the size of DelegationTokenRenewer event queue in case of too many pending events

[ https://issues.apache.org/jira/browse/YARN-10726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313195#comment-17313195 ] Qi Zhu commented on YARN-10726: --- Thanks [~pbacsko] for commit.:D > Log the size of Delegat

[jira] [Commented] (YARN-10637) We should support fs to cs support for auto refresh queues when conf changed, after YARN-10623 finished.

[ https://issues.apache.org/jira/browse/YARN-10637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313141#comment-17313141 ] Qi Zhu commented on YARN-10637: ---  [~pbacsko] [~gandras] If you any advice about this, just

[jira] [Commented] (YARN-10726) Log the size of DelegationTokenRenewer event queue in case of too many pending events

[ https://issues.apache.org/jira/browse/YARN-10726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313139#comment-17313139 ] Qi Zhu commented on YARN-10726: --- Thanks [~pbacsko] for your review and suggestion. You con

[jira] [Updated] (YARN-10726) Log the size of DelegationTokenRenewer event queue in case of too many pending events

[ https://issues.apache.org/jira/browse/YARN-10726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-10726: -- Attachment: YARN-10726.002.patch > Log the size of DelegationTokenRenewer event queue in case of too many > pe

[jira] [Commented] (YARN-10714) Remove dangling dynamic queues on reinitialization

[ https://issues.apache.org/jira/browse/YARN-10714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313029#comment-17313029 ] Qi Zhu commented on YARN-10714: --- Thanks [~gandras] for patch. The latest patch LGTM +1. W

[jira] [Commented] (YARN-10726) We should log size of pending DelegationTokenRenewerEvent queue, when pending too many events.

[ https://issues.apache.org/jira/browse/YARN-10726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313009#comment-17313009 ] Qi Zhu commented on YARN-10726: --- cc [~pbacsko] [~gandras]  Actually there are no any monit

[jira] [Comment Edited] (YARN-10726) We should log size of pending DelegationTokenRenewerEvent queue, when pending too many events.

[ https://issues.apache.org/jira/browse/YARN-10726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313009#comment-17313009 ] Qi Zhu edited comment on YARN-10726 at 4/1/21, 8:46 AM: cc [~pbac

[jira] [Commented] (YARN-9618) NodeListManager event improvement

[ https://issues.apache.org/jira/browse/YARN-9618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313006#comment-17313006 ] Qi Zhu commented on YARN-9618: -- Thanks [~pbacsko] [~gandras] for confirm. > NodeListManager

[jira] [Updated] (YARN-10726) We should log size of pending DelegationTokenRenewerEvent queue, when pending too many events.

[ https://issues.apache.org/jira/browse/YARN-10726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu updated YARN-10726: -- Issue Type: Improvement (was: Bug) > We should log size of pending DelegationTokenRenewerEvent queue, when pen

[jira] [Created] (YARN-10726) We should log size of pending DelegationTokenRenewerEvent queue, when pending too many events.

Qi Zhu created YARN-10726: - Summary: We should log size of pending DelegationTokenRenewerEvent queue, when pending too many events. Key: YARN-10726 URL: https://issues.apache.org/jira/browse/YARN-10726 Projec

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