[jira] [Created] (YARN-10745) Change Log level from info to debug for few logs and remove unnecessary debuglog checks

D M Murali Krishna Reddy created YARN-10745: --- Summary: Change Log level from info to debug for few logs and remove unnecessary debuglog checks Key: YARN-10745 URL:

[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=17325442#comment-17325442 ] Qi Zhu commented on YARN-10715: --- Thanks [~ebadger] for reply. It make sense to me. I will close it now. :)

[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=17325438#comment-17325438 ] Qi Zhu commented on YARN-10723: --- [~ebadger] Sure, i uploaded 005 patch to trigger jenkins. > Change CS

[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=17325432#comment-17325432 ] Qi Zhu edited comment on YARN-10743 at 4/20/21, 3:04 AM: - Thanks [~ebadger] for

[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=17325432#comment-17325432 ] Qi Zhu edited comment on YARN-10743 at 4/20/21, 3:02 AM: - Thanks [~ebadger] for

[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=17325432#comment-17325432 ] Qi Zhu commented on YARN-10743: --- Thanks [~ebadger] for reply. One case in our cluster : If the container

[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

[jira] [Updated] (YARN-10744) add more doc for yarn.federation.policy-manager-params

[ https://issues.apache.org/jira/browse/YARN-10744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated YARN-10744: -- Labels: pull-request-available (was: ) > add more doc for

[jira] [Created] (YARN-10744) add more doc for yarn.federation.policy-manager-params

chaosju created YARN-10744: -- Summary: add more doc for yarn.federation.policy-manager-params Key: YARN-10744 URL: https://issues.apache.org/jira/browse/YARN-10744 Project: Hadoop YARN Issue Type:

[jira] [Updated] (YARN-10460) Upgrading to JUnit 4.13 causes tests in TestNodeStatusUpdater to fail

[ https://issues.apache.org/jira/browse/YARN-10460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-10460: --- Fix Version/s: 2.10.2 3.1.5 Thanks for the review, [~Jim_Brennan]. The spotbugs

[jira] [Commented] (YARN-7769) FS QueueManager should not create default queue at init

[ https://issues.apache.org/jira/browse/YARN-7769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17325396#comment-17325396 ] Wilfred Spiegelenburg commented on YARN-7769: - Code change looks good. This does however also

[jira] [Commented] (YARN-9586) [QA] Need more doc for yarn.federation.policy-manager-params when LoadBasedRouterPolicy is used

[ https://issues.apache.org/jira/browse/YARN-9586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17325394#comment-17325394 ] chaosju commented on YARN-9586: --- cc [~qiuliang988] > [QA] Need more doc for

[jira] [Commented] (YARN-9586) [QA] Need more doc for yarn.federation.policy-manager-params when LoadBasedRouterPolicy is used

[ https://issues.apache.org/jira/browse/YARN-9586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17325393#comment-17325393 ] chaosju commented on YARN-9586: ---

[jira] [Commented] (YARN-10460) Upgrading to JUnit 4.13 causes tests in TestNodeStatusUpdater to fail

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

[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=17325387#comment-17325387 ] Eric Badger commented on YARN-10715: Finally getting around to looking at this and I don't think

[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=17325343#comment-17325343 ] Eric Badger commented on YARN-10743: I have the same concern as [~Jim_Brennan]. If the flink logs are

[jira] [Commented] (YARN-10460) Upgrading to JUnit 4.13 causes tests in TestNodeStatusUpdater to fail

[ https://issues.apache.org/jira/browse/YARN-10460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17325332#comment-17325332 ] Jim Brennan commented on YARN-10460: +1 on the branch-2.10 patch. > Upgrading to JUnit 4.13 causes

[jira] [Commented] (YARN-10460) Upgrading to JUnit 4.13 causes tests in TestNodeStatusUpdater to fail

[ https://issues.apache.org/jira/browse/YARN-10460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17325329#comment-17325329 ] Eric Badger commented on YARN-10460: Posting a branch-2.10 patch that doesn't use a lambda expression

[jira] [Updated] (YARN-10460) Upgrading to JUnit 4.13 causes tests in TestNodeStatusUpdater to fail

[ https://issues.apache.org/jira/browse/YARN-10460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-10460: --- Attachment: YARN-10460-branch-2.10.002.patch > Upgrading to JUnit 4.13 causes tests in

[jira] [Comment Edited] (YARN-10460) Upgrading to JUnit 4.13 causes tests in TestNodeStatusUpdater to fail

[ https://issues.apache.org/jira/browse/YARN-10460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17325291#comment-17325291 ] Eric Badger edited comment on YARN-10460 at 4/19/21, 8:26 PM: -- Thanks for

[jira] [Updated] (YARN-10460) Upgrading to JUnit 4.13 causes tests in TestNodeStatusUpdater to fail

[ https://issues.apache.org/jira/browse/YARN-10460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-10460: --- Fix Version/s: 3.2.3 Thanks for the review, [~Jim_Brennan]! I've committed the 3.2 patch to

[jira] [Commented] (YARN-10460) Upgrading to JUnit 4.13 causes tests in TestNodeStatusUpdater to fail

[ https://issues.apache.org/jira/browse/YARN-10460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17325278#comment-17325278 ] Jim Brennan commented on YARN-10460: +1 on the branch-3.2 patch. Looks good to me. > Upgrading to

[jira] [Commented] (YARN-10460) Upgrading to JUnit 4.13 causes tests in TestNodeStatusUpdater to fail

[ https://issues.apache.org/jira/browse/YARN-10460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17325231#comment-17325231 ] Eric Badger commented on YARN-10460: The unit tests seem unrelated and don't fail for me locally.

[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=17325210#comment-17325210 ] Eric Badger commented on YARN-10723: Looks like it still never ran. [~zhuqi], can you re-upload the

[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=17325109#comment-17325109 ] Qi Zhu edited comment on YARN-10743 at 4/19/21, 3:22 PM: - Thanks [~Jim_Brennan] 

[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=17325109#comment-17325109 ] Qi Zhu edited comment on YARN-10743 at 4/19/21, 3:21 PM: - Thanks [~Jim_Brennan] 

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

[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=17325109#comment-17325109 ] Qi Zhu commented on YARN-10743: --- Thanks [~Jim_Brennan] for reply. But in our cluster, some flink log size

[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=17325102#comment-17325102 ] Jim Brennan commented on YARN-10743: I don't think this is necessary. The logs may actually be

[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] [Updated] (YARN-9906) When setting multi volumes throurh the "YARN_CONTAINER_RUNTIME_DOCKER_MOUNTS" setting is not valid

[ https://issues.apache.org/jira/browse/YARN-9906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated YARN-9906: - Labels: pull-request-available (was: ) > When setting multi volumes throurh the

[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=17324779#comment-17324779 ] Zhanqi Cai commented on YARN-10739: --- LGTM.  > GenericEventHandler.printEventQueueDetails cause RM