[jira] [Updated] (YARN-10453) Add partition resource info to get-node-labels and label-mappings api responses
[ https://issues.apache.org/jira/browse/YARN-10453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-10453: Attachment: YARN-10453.003.patch > Add partition resource info to get-node-labels and label-mappings api > responses > --- > > Key: YARN-10453 > URL: https://issues.apache.org/jira/browse/YARN-10453 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Major > Attachments: YARN-10453.001.patch, YARN-10453.002.patch, > YARN-10453.003.patch > > > This jira will add partition resource info to responses get-node-labels and > label-mappings apis. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10453) Add partition resource info to get-node-labels and label-mappings api responses
[ https://issues.apache.org/jira/browse/YARN-10453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17208624#comment-17208624 ] Akhil PB commented on YARN-10453: - The unit test failure is not related to the patch. > Add partition resource info to get-node-labels and label-mappings api > responses > --- > > Key: YARN-10453 > URL: https://issues.apache.org/jira/browse/YARN-10453 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Major > Attachments: YARN-10453.001.patch, YARN-10453.002.patch > > > This jira will add partition resource info to responses get-node-labels and > label-mappings apis. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10453) Add partition resource info to get-node-labels and label-mappings api responses
[ https://issues.apache.org/jira/browse/YARN-10453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-10453: Attachment: YARN-10453.002.patch > Add partition resource info to get-node-labels and label-mappings api > responses > --- > > Key: YARN-10453 > URL: https://issues.apache.org/jira/browse/YARN-10453 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Major > Attachments: YARN-10453.001.patch, YARN-10453.002.patch > > > This jira will add partition resource info to responses get-node-labels and > label-mappings apis. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10453) Add partition resource info to get-node-labels and label-mappings api responses
[ https://issues.apache.org/jira/browse/YARN-10453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17208489#comment-17208489 ] Akhil PB commented on YARN-10453: - [~tanu.ajmera] could you please review this patch? > Add partition resource info to get-node-labels and label-mappings api > responses > --- > > Key: YARN-10453 > URL: https://issues.apache.org/jira/browse/YARN-10453 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Major > Attachments: YARN-10453.001.patch > > > This jira will add partition resource info to responses get-node-labels and > label-mappings apis. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (YARN-10453) Add partition resource info to get-node-labels and label-mappings api responses
[ https://issues.apache.org/jira/browse/YARN-10453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17208489#comment-17208489 ] Akhil PB edited comment on YARN-10453 at 10/6/20, 5:21 AM: --- Hi [~tanu.ajmera], could you please review this patch? was (Author: akhilpb): [~tanu.ajmera] could you please review this patch? > Add partition resource info to get-node-labels and label-mappings api > responses > --- > > Key: YARN-10453 > URL: https://issues.apache.org/jira/browse/YARN-10453 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Major > Attachments: YARN-10453.001.patch > > > This jira will add partition resource info to responses get-node-labels and > label-mappings apis. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10453) Add partition resource info to get-node-labels and label-mappings api responses
[ https://issues.apache.org/jira/browse/YARN-10453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17207967#comment-17207967 ] Akhil PB commented on YARN-10453: - Hi [~sunilg], [~prabhujoseph], Could you please review the patch. > Add partition resource info to get-node-labels and label-mappings api > responses > --- > > Key: YARN-10453 > URL: https://issues.apache.org/jira/browse/YARN-10453 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Major > Attachments: YARN-10453.001.patch > > > This jira will add partition resource info to responses get-node-labels and > label-mappings apis. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10453) Add partition resource info to get-node-labels and label-mappings api responses
[ https://issues.apache.org/jira/browse/YARN-10453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-10453: Attachment: YARN-10453.001.patch > Add partition resource info to get-node-labels and label-mappings api > responses > --- > > Key: YARN-10453 > URL: https://issues.apache.org/jira/browse/YARN-10453 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Major > Attachments: YARN-10453.001.patch > > > This jira will add partition resource info to responses get-node-labels and > label-mappings apis. > cc: [~sunilg] [~wangda] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10453) Add partition resource info to get-node-labels and label-mappings api responses
[ https://issues.apache.org/jira/browse/YARN-10453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-10453: Description: This jira will add partition resource info to responses get-node-labels and label-mappings apis. was: This jira will add partition resource info to responses get-node-labels and label-mappings apis. cc: [~sunilg] [~wangda] > Add partition resource info to get-node-labels and label-mappings api > responses > --- > > Key: YARN-10453 > URL: https://issues.apache.org/jira/browse/YARN-10453 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Major > Attachments: YARN-10453.001.patch > > > This jira will add partition resource info to responses get-node-labels and > label-mappings apis. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10453) Add partition resource info to get-node-labels and label-mappings api responses
[ https://issues.apache.org/jira/browse/YARN-10453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-10453: Description: This jira will add partition resource info to responses get-node-labels and label-mappings apis. cc: [~sunilg] [~wangda] was: This jira will add partition info of resources to responses get-node-labels and label-mappings apis. cc: [~sunilg] [~wangda] > Add partition resource info to get-node-labels and label-mappings api > responses > --- > > Key: YARN-10453 > URL: https://issues.apache.org/jira/browse/YARN-10453 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Major > > This jira will add partition resource info to responses get-node-labels and > label-mappings apis. > cc: [~sunilg] [~wangda] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-10453) Add partition resource info to get-node-labels and label-mappings api responses
Akhil PB created YARN-10453: --- Summary: Add partition resource info to get-node-labels and label-mappings api responses Key: YARN-10453 URL: https://issues.apache.org/jira/browse/YARN-10453 Project: Hadoop YARN Issue Type: Bug Components: yarn Reporter: Akhil PB Assignee: Akhil PB This jira will add partition info of resources to responses get-node-labels and label-mappings apis. cc: [~sunilg] [~wangda] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10452) YARN scheduler response returns invalid values for capacity, maxCapacity and absoluteMaxCapacity
[ https://issues.apache.org/jira/browse/YARN-10452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-10452: Attachment: yarn_scheduler_response_incorrect_partition_capacity.json > YARN scheduler response returns invalid values for capacity, maxCapacity and > absoluteMaxCapacity > > > Key: YARN-10452 > URL: https://issues.apache.org/jira/browse/YARN-10452 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn >Reporter: Akhil PB >Priority: Major > Attachments: yarn_scheduler_response_incorrect_partition_capacity.json > > > When there are no nodes in the default partition, YARN scheduler response > returns invalid values for capacities as listed below. > - capacity is INF > - maxCapacity is NaN > - absoluteMaxCapacity is NaN > Attached the YARN scheduler response json. > cc: [~sunilg] [~wangda] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-10452) YARN scheduler response returns invalid values for capacity, maxCapacity and absoluteMaxCapacity
Akhil PB created YARN-10452: --- Summary: YARN scheduler response returns invalid values for capacity, maxCapacity and absoluteMaxCapacity Key: YARN-10452 URL: https://issues.apache.org/jira/browse/YARN-10452 Project: Hadoop YARN Issue Type: Bug Components: yarn Reporter: Akhil PB When there are no nodes in the default partition, YARN scheduler response returns invalid values for capacities as listed below. - capacity is INF - maxCapacity is NaN - absoluteMaxCapacity is NaN Attached the YARN scheduler response json. cc: [~sunilg] [~wangda] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-10436) Create RM rest api endpoint to get list of cluster configurations
Akhil PB created YARN-10436: --- Summary: Create RM rest api endpoint to get list of cluster configurations Key: YARN-10436 URL: https://issues.apache.org/jira/browse/YARN-10436 Project: Hadoop YARN Issue Type: Sub-task Components: yarn Reporter: Akhil PB Assignee: Akhil PB The current /conf endpoint returns one config at a time and this would require multiple api calls to get multiple configurations. This jira intends to fix this issue by adding new rest api endpoint /cluster-conf where user can send queryparam like name=config_1,confg_2 to get multiple configurations. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10436) Create RM rest api endpoint to get list of cluster configurations
[ https://issues.apache.org/jira/browse/YARN-10436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-10436: Description: The current /conf endpoint returns one config at a time and this would require multiple api calls to get multiple configurations. This jira intends to fix this issue by adding new rest api endpoint /cluster-conf where user can send queryparam like name=config_1,confg_2 to get multiple configurations. cc: [~sunilg] was:The current /conf endpoint returns one config at a time and this would require multiple api calls to get multiple configurations. This jira intends to fix this issue by adding new rest api endpoint /cluster-conf where user can send queryparam like name=config_1,confg_2 to get multiple configurations. > Create RM rest api endpoint to get list of cluster configurations > - > > Key: YARN-10436 > URL: https://issues.apache.org/jira/browse/YARN-10436 > Project: Hadoop YARN > Issue Type: Sub-task > Components: yarn >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Major > > The current /conf endpoint returns one config at a time and this would > require multiple api calls to get multiple configurations. This jira intends > to fix this issue by adding new rest api endpoint /cluster-conf where user > can send queryparam like name=config_1,confg_2 to get multiple configurations. > cc: [~sunilg] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10435) Upgrade ui2 framework ember 2.x to ember 3.20
[ https://issues.apache.org/jira/browse/YARN-10435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-10435: Summary: Upgrade ui2 framework ember 2.x to ember 3.20 (was: Upgrade ember 2.x to ember 3.20) > Upgrade ui2 framework ember 2.x to ember 3.20 > - > > Key: YARN-10435 > URL: https://issues.apache.org/jira/browse/YARN-10435 > Project: Hadoop YARN > Issue Type: Sub-task > Components: yarn-ui-v2 >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Major > > This is the full rewrite of the current YARN UI2 framework ember 2.x to ember > 3.20. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-10435) Upgrade ember 2.x to ember 3.20
Akhil PB created YARN-10435: --- Summary: Upgrade ember 2.x to ember 3.20 Key: YARN-10435 URL: https://issues.apache.org/jira/browse/YARN-10435 Project: Hadoop YARN Issue Type: Sub-task Components: yarn-ui-v2 Reporter: Akhil PB Assignee: Akhil PB This is the full rewrite of the current YARN UI2 framework ember 2.x to ember 3.20. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10429) [Umbrella] YARN UI2 Improvements
[ https://issues.apache.org/jira/browse/YARN-10429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17192637#comment-17192637 ] Akhil PB commented on YARN-10429: - [~sunilg] Yes, we will cover upgrade of Yarn UI2 to ember 3.20 (latest recommended LTS ember version) in this umbrella. > [Umbrella] YARN UI2 Improvements > > > Key: YARN-10429 > URL: https://issues.apache.org/jira/browse/YARN-10429 > Project: Hadoop YARN > Issue Type: Improvement > Components: yarn-ui-v2 >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Major > > cc: [~sunilg] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10429) [Umbrella] YARN UI2 Improvements
[ https://issues.apache.org/jira/browse/YARN-10429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-10429: Summary: [Umbrella] YARN UI2 Improvements (was: [Umbrella] YARN UI2 Upgrades ) > [Umbrella] YARN UI2 Improvements > > > Key: YARN-10429 > URL: https://issues.apache.org/jira/browse/YARN-10429 > Project: Hadoop YARN > Issue Type: Improvement > Components: yarn-ui-v2 >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Major > > cc: [~sunilg] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10429) [Umbrella] YARN UI2 Upgrades
[ https://issues.apache.org/jira/browse/YARN-10429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-10429: Summary: [Umbrella] YARN UI2 Upgrades (was: [Umbrella] YARN UI2 Improvements ) > [Umbrella] YARN UI2 Upgrades > - > > Key: YARN-10429 > URL: https://issues.apache.org/jira/browse/YARN-10429 > Project: Hadoop YARN > Issue Type: Improvement > Components: yarn-ui-v2 >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Major > > cc: [~sunilg] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-10429) [Umbrella] YARN UI2 Improvements
Akhil PB created YARN-10429: --- Summary: [Umbrella] YARN UI2 Improvements Key: YARN-10429 URL: https://issues.apache.org/jira/browse/YARN-10429 Project: Hadoop YARN Issue Type: Improvement Components: yarn-ui-v2 Reporter: Akhil PB Assignee: Akhil PB cc: [~sunilg] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-1806) webUI update to allow end users to request thread dump
[ https://issues.apache.org/jira/browse/YARN-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17184949#comment-17184949 ] Akhil PB commented on YARN-1806: [~sahuja] The initial patch looks good. Any improvements could be done in follow up jiras. > webUI update to allow end users to request thread dump > -- > > Key: YARN-1806 > URL: https://issues.apache.org/jira/browse/YARN-1806 > Project: Hadoop YARN > Issue Type: Sub-task > Components: nodemanager >Reporter: Ming Ma >Assignee: Siddharth Ahuja >Priority: Major > Attachments: YARN-1806.001.patch > > > Both individual container gage and containers page will support this. After > end user clicks on the request link, they can follow to get to stdout page > for the thread dump content. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-10239) Capacity is zero for auto created leaf queues after leaf-queue-template.capacity has been updated
Akhil PB created YARN-10239: --- Summary: Capacity is zero for auto created leaf queues after leaf-queue-template.capacity has been updated Key: YARN-10239 URL: https://issues.apache.org/jira/browse/YARN-10239 Project: Hadoop YARN Issue Type: Bug Reporter: Akhil PB In the scheduler response, the capacity of the auto created leaf queue became zero after leaf-queue-template.capacity of managed parent queue has been updated.\ cc: [~sunilg] [~wangda] [~prabhujoseph] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10239) Capacity is zero for auto created leaf queues after leaf-queue-template.capacity has been updated
[ https://issues.apache.org/jira/browse/YARN-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-10239: Description: In the scheduler response, the capacity of the auto created leaf queue became zero after leaf-queue-template.capacity of managed parent queue has been updated. cc: [~sunilg] [~wangda] [~prabhujoseph] was: In the scheduler response, the capacity of the auto created leaf queue became zero after leaf-queue-template.capacity of managed parent queue has been updated.\ cc: [~sunilg] [~wangda] [~prabhujoseph] > Capacity is zero for auto created leaf queues after > leaf-queue-template.capacity has been updated > - > > Key: YARN-10239 > URL: https://issues.apache.org/jira/browse/YARN-10239 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Akhil PB >Priority: Major > > In the scheduler response, the capacity of the auto created leaf queue became > zero after leaf-queue-template.capacity of managed parent queue has been > updated. > cc: [~sunilg] [~wangda] [~prabhujoseph] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10233) [YARN UI2] No Logs were found in "YARN Daemon Logs" page
[ https://issues.apache.org/jira/browse/YARN-10233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-10233: Attachment: YARN_UI2_Tools_Daemon_Logs_Page_Fixed.png > [YARN UI2] No Logs were found in "YARN Daemon Logs" page > > > Key: YARN-10233 > URL: https://issues.apache.org/jira/browse/YARN-10233 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Blocker > Fix For: 3.3.0 > > Attachments: YARN-10233.001.patch, > YARN_UI2_Tools_Daemon_Logs_Page_Fixed.png > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10233) [YARN UI2] No Logs were found in "YARN Daemon Logs" page
[ https://issues.apache.org/jira/browse/YARN-10233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-10233: Attachment: (was: YARN_UI2_Tools_Daeon_Logs_Page_Fixed.png) > [YARN UI2] No Logs were found in "YARN Daemon Logs" page > > > Key: YARN-10233 > URL: https://issues.apache.org/jira/browse/YARN-10233 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Blocker > Fix For: 3.3.0 > > Attachments: YARN-10233.001.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10233) [YARN UI2] No Logs were found in "YARN Daemon Logs" page
[ https://issues.apache.org/jira/browse/YARN-10233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-10233: Attachment: YARN_UI2_Tools_Daeon_Logs_Page_Fixed.png > [YARN UI2] No Logs were found in "YARN Daemon Logs" page > > > Key: YARN-10233 > URL: https://issues.apache.org/jira/browse/YARN-10233 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Blocker > Fix For: 3.3.0 > > Attachments: YARN-10233.001.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10233) [YARN UI2] No Logs were found in "YARN Daemon Logs" page
[ https://issues.apache.org/jira/browse/YARN-10233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17083452#comment-17083452 ] Akhil PB commented on YARN-10233: - [~sunilg] [~prabhujoseph] Could you please review the patch. > [YARN UI2] No Logs were found in "YARN Daemon Logs" page > > > Key: YARN-10233 > URL: https://issues.apache.org/jira/browse/YARN-10233 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Blocker > Fix For: 3.3.0 > > Attachments: YARN-10233.001.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10233) [YARN UI2] No Logs were found in "YARN Daemon Logs" page
[ https://issues.apache.org/jira/browse/YARN-10233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-10233: Attachment: YARN-10233.001.patch > [YARN UI2] No Logs were found in "YARN Daemon Logs" page > > > Key: YARN-10233 > URL: https://issues.apache.org/jira/browse/YARN-10233 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Blocker > Fix For: 3.3.0 > > Attachments: YARN-10233.001.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Resolved] (YARN-9710) [UI2] Yarn Daemon Logs displays the URL instead of log name
[ https://issues.apache.org/jira/browse/YARN-9710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB resolved YARN-9710. Resolution: Duplicate > [UI2] Yarn Daemon Logs displays the URL instead of log name > --- > > Key: YARN-9710 > URL: https://issues.apache.org/jira/browse/YARN-9710 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.2.0 >Reporter: Prabhu Joseph >Assignee: Akhil PB >Priority: Minor > Attachments: Screen Shot 2019-07-26 at 8.53.50 PM.png > > > Yarn Daemon Logs displays the URL instead of log name. > !Screen Shot 2019-07-26 at 8.53.50 PM.png|height=300! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-9710) [UI2] Yarn Daemon Logs displays the URL instead of log name
[ https://issues.apache.org/jira/browse/YARN-9710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17083231#comment-17083231 ] Akhil PB commented on YARN-9710: This will be fixed in YARN-10233 > [UI2] Yarn Daemon Logs displays the URL instead of log name > --- > > Key: YARN-9710 > URL: https://issues.apache.org/jira/browse/YARN-9710 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.2.0 >Reporter: Prabhu Joseph >Assignee: Akhil PB >Priority: Minor > Attachments: Screen Shot 2019-07-26 at 8.53.50 PM.png > > > Yarn Daemon Logs displays the URL instead of log name. > !Screen Shot 2019-07-26 at 8.53.50 PM.png|height=300! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Assigned] (YARN-9710) [UI2] Yarn Daemon Logs displays the URL instead of log name
[ https://issues.apache.org/jira/browse/YARN-9710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB reassigned YARN-9710: -- Assignee: Akhil PB (was: Prabhu Joseph) > [UI2] Yarn Daemon Logs displays the URL instead of log name > --- > > Key: YARN-9710 > URL: https://issues.apache.org/jira/browse/YARN-9710 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.2.0 >Reporter: Prabhu Joseph >Assignee: Akhil PB >Priority: Minor > Attachments: Screen Shot 2019-07-26 at 8.53.50 PM.png > > > Yarn Daemon Logs displays the URL instead of log name. > !Screen Shot 2019-07-26 at 8.53.50 PM.png|height=300! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10233) [YARN UI2] No Logs were found in "YARN Daemon Logs" page
[ https://issues.apache.org/jira/browse/YARN-10233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-10233: Summary: [YARN UI2] No Logs were found in "YARN Daemon Logs" page (was: [YARN UI2] No Logs were found in Tools - Daemon Logs page) > [YARN UI2] No Logs were found in "YARN Daemon Logs" page > > > Key: YARN-10233 > URL: https://issues.apache.org/jira/browse/YARN-10233 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Major > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-10233) [YARN UI2] No Logs were found in Tools - Daemon Logs page
Akhil PB created YARN-10233: --- Summary: [YARN UI2] No Logs were found in Tools - Daemon Logs page Key: YARN-10233 URL: https://issues.apache.org/jira/browse/YARN-10233 Project: Hadoop YARN Issue Type: Bug Components: yarn-ui-v2 Reporter: Akhil PB Assignee: Akhil PB Fix For: 3.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-10222) Update YARN RM Rest API doc with Node Label APIs
Akhil PB created YARN-10222: --- Summary: Update YARN RM Rest API doc with Node Label APIs Key: YARN-10222 URL: https://issues.apache.org/jira/browse/YARN-10222 Project: Hadoop YARN Issue Type: Bug Components: docs Reporter: Akhil PB YARN RM Rest API doc does not have API details of YARN Node Labels. There are many APIs related to YARN Node Labels. Should update the doc with Node Label APIs. cc: [~sunilg] [~wangda] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-10211) [YARN UI2] Queue selection is not highlighted on first time in queues page
Akhil PB created YARN-10211: --- Summary: [YARN UI2] Queue selection is not highlighted on first time in queues page Key: YARN-10211 URL: https://issues.apache.org/jira/browse/YARN-10211 Project: Hadoop YARN Issue Type: Bug Reporter: Akhil PB Assignee: Akhil PB -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (YARN-10198) [managedParent].%primary_group mapping rule doesn't work after YARN-9868
[
https://issues.apache.org/jira/browse/YARN-10198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17060683#comment-17060683
]
Akhil PB edited comment on YARN-10198 at 3/17/20, 7:40 AM:
---
Expected behaviour:
# *[managedParent].%primary_group*
** Should not create queue named *%primary_group* under *[managedParent]* if
leaf queue named *%primary_group* already exists.
** Should create new child queue under *[managedParent]* if leaf queue named
*%primary_group* does not exists.
# *[managedParent].%secondary_group*
** Should not create queue named *%secondary_group* under *[managedParent]* if
leaf queue named *%secondary_group* already exists.
** Should create new child queue under *[managedParent]* if leaf queue named
*%secondary_group* does not exists.
** If the user does not have *%secondary_group*, then the app should be
submitted to the "default" queue (I guess based on the below static mapping).
Note that for current static mappings like *u:%user:%primary_group* and
*u:%user:%secondary_group*, following is the behavior and works as expected.
# *u:%user:%primary_group*
** App submitted when leaf queue named *%primary_group* is present
** App failed when leaf queue named *%primary_group* is not present or stopped
# *u:%user:%secondary_group*
** App submitted when leaf queue named *%secondary_group* is present
** App submitted to "default" queue when leaf queue named *%secondary_group* is
not present
Please share your thoughts if I am missing something.
cc: [~sunilg] [~prabhujoseph] [~pbacsko]
was (Author: akhilpb):
Expected behavior:
# *[managedParent].%primary_group*
** Should not create queue named *%primary_group* under *[managedParent]* if
leaf queue named *%primary_group* already exists.
** Should create new child queue under *[managedParent]* if leaf queue named
*%primary_group* does not exists.
# *[managedParent].%secondary_group*
** Should not create queue named *%secondary_group* under *[managedParent]* if
leaf queue named *%secondary_group* already exists.
** Should create new child queue under *[managedParent]* if leaf queue named
*%secondary_group* does not exists.
** If the user does not have *%secondary_group*, then the app should be
submitted to the "default" queue (I guess based on the below).
Note that for current static mappings like *u:%user:%primary_group* and
*u:%user:%secondary_group*, following is the behavior and works as expected.
# *u:%user:%primary_group*
** App submitted when leaf queue named *%primary_group* is present
** App failed when leaf queue named *%primary_group* is not present or stopped
# *u:%user:%secondary_group*
** App submitted when leaf queue named *%secondary_group* is present
** App submitted to "default" queue when leaf queue named *%secondary_group* is
not present
Please share your thoughts if I am missing something.
cc: [~sunilg] [~prabhujoseph] [~pbacsko]
> [managedParent].%primary_group mapping rule doesn't work after YARN-9868
>
>
> Key: YARN-10198
> URL: https://issues.apache.org/jira/browse/YARN-10198
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacity scheduler
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
>
> YARN-9868 introduced an unnecessary check if we have the following placement
> rule:
> [managedParentQueue].%primary_group
> Here, {{%primary_group}} is expected to be created if it doesn't exist.
> However, there is this validation code which is not necessary:
> {noformat}
> } else if (mapping.getQueue().equals(PRIMARY_GROUP_MAPPING)) {
> if (this.queueManager
> .getQueue(groups.getGroups(user).get(0)) != null) {
> return getPlacementContext(mapping,
> groups.getGroups(user).get(0));
> } else {
> return null;
> }
> {noformat}
> We should revert this part to the original version:
> {noformat}
> } else if (mapping.queue.equals(PRIMARY_GROUP_MAPPING)) {
> return getPlacementContext(mapping,
> groups.getGroups(user).get(0));
> }
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (YARN-10198) [managedParent].%primary_group mapping rule doesn't work after YARN-9868
[
https://issues.apache.org/jira/browse/YARN-10198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17060683#comment-17060683
]
Akhil PB edited comment on YARN-10198 at 3/17/20, 7:34 AM:
---
Expected behavior:
# *[managedParent].%primary_group*
** Should not create queue named *%primary_group* under *[managedParent]* if
leaf queue named *%primary_group* already exists.
** Should create new child queue under *[managedParent]* if leaf queue named
*%primary_group* does not exists.
# *[managedParent].%secondary_group*
** Should not create queue named *%secondary_group* under *[managedParent]* if
leaf queue named *%secondary_group* already exists.
** Should create new child queue under *[managedParent]* if leaf queue named
*%secondary_group* does not exists.
** If the user does not have *%secondary_group*, then the app should be
submitted to the "default" queue (I guess based on the below).
Note that for current static mappings like *u:%user:%primary_group* and
*u:%user:%secondary_group*, following is the behavior and works as expected.
# *u:%user:%primary_group*
** App submitted when leaf queue named *%primary_group* is present
** App failed when leaf queue named *%primary_group* is not present or stopped
# *u:%user:%secondary_group*
** App submitted when leaf queue named *%secondary_group* is present
** App submitted to "default" queue when leaf queue named *%secondary_group* is
not present
Please share your thoughts if I am missing something.
cc: [~sunilg] [~prabhujoseph] [~pbacsko]
was (Author: akhilpb):
Expected behavior:
# *[managedParent].%primary_group*
** Should not create queue named *%primary_group* under *[managedParent]* if
leaf queue named *%primary_group* already exists.
** Should create new child queue under *[managedParent]* if leaf queue named
*%primary_group* does not exists.
# *[managedParent].%secondary_group*
** Should not create queue named *%secondary_group* under *[managedParent]* if
leaf queue named *%secondary_group* already exists.
** Should create new child queue under *[managedParent]* if leaf queue named
*%secondary_group* does not exists.
Note that for current static mappings like *u:%user:%primary_group* and
*u:%user:%secondary_group*, following is the behavior and works as expected.
# *u:%user:%primary_group*
** App submitted when leaf queue named *%primary_group* is present
** App failed when leaf queue named *%primary_group* is not present or stopped
# *u:%user:%secondary_group*
** App submitted when leaf queue named *%secondary_group* is present
** App submitted to "default" queue when leaf queue named *%secondary_group* is
not present
Please share your thoughts if I am missing something.
cc: [~sunilg] [~prabhujoseph] [~pbacsko]
> [managedParent].%primary_group mapping rule doesn't work after YARN-9868
>
>
> Key: YARN-10198
> URL: https://issues.apache.org/jira/browse/YARN-10198
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacity scheduler
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
>
> YARN-9868 introduced an unnecessary check if we have the following placement
> rule:
> [managedParentQueue].%primary_group
> Here, {{%primary_group}} is expected to be created if it doesn't exist.
> However, there is this validation code which is not necessary:
> {noformat}
> } else if (mapping.getQueue().equals(PRIMARY_GROUP_MAPPING)) {
> if (this.queueManager
> .getQueue(groups.getGroups(user).get(0)) != null) {
> return getPlacementContext(mapping,
> groups.getGroups(user).get(0));
> } else {
> return null;
> }
> {noformat}
> We should revert this part to the original version:
> {noformat}
> } else if (mapping.queue.equals(PRIMARY_GROUP_MAPPING)) {
> return getPlacementContext(mapping,
> groups.getGroups(user).get(0));
> }
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (YARN-10198) [managedParent].%primary_group mapping rule doesn't work after YARN-9868
[
https://issues.apache.org/jira/browse/YARN-10198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17060683#comment-17060683
]
Akhil PB edited comment on YARN-10198 at 3/17/20, 7:30 AM:
---
Expected behavior:
# *[managedParent].%primary_group*
** Should not create queue named *%primary_group* under *[managedParent]* if
leaf queue named *%primary_group* already exists.
** Should create new child queue under *[managedParent]* if leaf queue named
*%primary_group* does not exists.
# *[managedParent].%secondary_group*
** Should not create queue named *%secondary_group* under *[managedParent]* if
leaf queue named *%secondary_group* already exists.
** Should create new child queue under *[managedParent]* if leaf queue named
*%secondary_group* does not exists.
Note that for current static mappings like *u:%user:%primary_group* and
*u:%user:%secondary_group*, following is the behavior and works as expected.
# *u:%user:%primary_group*
** App submitted when leaf queue named *%primary_group* is present
** App failed when leaf queue named *%primary_group* is not present or stopped
# *u:%user:%secondary_group*
** App submitted when leaf queue named *%secondary_group* is present
** App submitted to "default" queue when leaf queue named *%secondary_group* is
not present
Please share your thoughts if I am missing something.
cc: [~sunilg] [~prabhujoseph] [~pbacsko]
was (Author: akhilpb):
Expected behavior:
# *[managedParent].%primary_group*
** Should not create queue named *%primary_group* under *[managedParent]* if
leaf queue named *%primary_group* already exists.
** Should create new child queue under *[managedParent]* if leaf queue named
*%primary_group* does not exists.
# *[managedParent].%secondary_group*
** Should not create queue named *%secondary_group* under *[managedParent]* if
leaf queue named *%secondary_group* already exists.
** Should create new child queue under *[managedParent]* if leaf queue named
*%secondary_group* does not exists.
Note that for current static mappings like *u:%user:%primary_group* and
*u:%user:%secondary_group*, following is the behavior and works as expected.
# *u:%user:%primary_group*
** App submitted when leaf queue named *%primary_group* is present
** App failed when leaf queue named *%primary_group* is not present or stopped
# *u:%user:%secondary_group*
** App submitted when leaf queue named *%secondary_group* is present
** App submitted to "default" queue when leaf queue named *%secondary_group* is
not present
Please share your thoughts if I am missing something.
cc: [~sunilg] [~prabhujoseph] [~pbacsko]
> [managedParent].%primary_group mapping rule doesn't work after YARN-9868
>
>
> Key: YARN-10198
> URL: https://issues.apache.org/jira/browse/YARN-10198
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacity scheduler
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
>
> YARN-9868 introduced an unnecessary check if we have the following placement
> rule:
> [managedParentQueue].%primary_group
> Here, {{%primary_group}} is expected to be created if it doesn't exist.
> However, there is this validation code which is not necessary:
> {noformat}
> } else if (mapping.getQueue().equals(PRIMARY_GROUP_MAPPING)) {
> if (this.queueManager
> .getQueue(groups.getGroups(user).get(0)) != null) {
> return getPlacementContext(mapping,
> groups.getGroups(user).get(0));
> } else {
> return null;
> }
> {noformat}
> We should revert this part to the original version:
> {noformat}
> } else if (mapping.queue.equals(PRIMARY_GROUP_MAPPING)) {
> return getPlacementContext(mapping,
> groups.getGroups(user).get(0));
> }
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (YARN-10198) [managedParent].%primary_group mapping rule doesn't work after YARN-9868
[
https://issues.apache.org/jira/browse/YARN-10198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17060683#comment-17060683
]
Akhil PB edited comment on YARN-10198 at 3/17/20, 7:30 AM:
---
Expected behavior:
# *[managedParent].%primary_group*
** Should not create queue named *%primary_group* under *[managedParent]* if
leaf queue named *%primary_group* already exists.
** Should create new child queue under *[managedParent]* if leaf queue named
*%primary_group* does not exists.
# *[managedParent].%secondary_group*
** Should not create queue named *%secondary_group* under *[managedParent]* if
leaf queue named *%secondary_group* already exists.
** Should create new child queue under *[managedParent]* if leaf queue named
*%secondary_group* does not exists.
Note that for current static mappings like *u:%user:%primary_group* and
*u:%user:%secondary_group*, following is the behavior and works as expected.
# *u:%user:%primary_group*
** App submitted when leaf queue named *%primary_group* is present
** App failed when leaf queue named *%primary_group* is not present or stopped
# *u:%user:%secondary_group*
** App submitted when leaf queue named *%secondary_group* is present
** App submitted to "default" queue when leaf queue named *%secondary_group* is
not present
Please share your thoughts if I am missing something.
cc: [~sunilg] [~prabhujoseph] [~pbacsko]
was (Author: akhilpb):
Expected behavior:
# *[managedParent].%primary_group*
** Should not create queue named *%primary_group* under *[managedParent]* if
leaf queue named *%primary_group* already exists.
** Should create new child queue under *[managedParent]* if leaf queue named
*%primary_group* does not exists.
# *[managedParent].%secondary_group*
** Should not create queue named *%secondary_group* under *[managedParent]* if
leaf queue named *%secondary_group* already exists.
** Should create new child queue under *[managedParent]* if leaf queue named
*%secondary_group* does not exists.
Note that for current static mappings like *u:%user:%primary_group* and
*u:%user:%secondary_group*, following is the behavior and works as expected.
# *u:%user:%primary_group*
** App submitted when leaf queue named *%primary_group* is present
** App failed when leaf queue named *%primary_group* is not present or stopped
# *u:%user:%secondary_group*
** App submitted when leaf queue named *%secondary_group* is present
** App submitted to "default" queue when leaf queue named *%secondary_group* is
not present
Please share your thoughts if I am missing something.
cc: [~sunilg] [~prabhujoseph] [~pbacsko]
> [managedParent].%primary_group mapping rule doesn't work after YARN-9868
>
>
> Key: YARN-10198
> URL: https://issues.apache.org/jira/browse/YARN-10198
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacity scheduler
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
>
> YARN-9868 introduced an unnecessary check if we have the following placement
> rule:
> [managedParentQueue].%primary_group
> Here, {{%primary_group}} is expected to be created if it doesn't exist.
> However, there is this validation code which is not necessary:
> {noformat}
> } else if (mapping.getQueue().equals(PRIMARY_GROUP_MAPPING)) {
> if (this.queueManager
> .getQueue(groups.getGroups(user).get(0)) != null) {
> return getPlacementContext(mapping,
> groups.getGroups(user).get(0));
> } else {
> return null;
> }
> {noformat}
> We should revert this part to the original version:
> {noformat}
> } else if (mapping.queue.equals(PRIMARY_GROUP_MAPPING)) {
> return getPlacementContext(mapping,
> groups.getGroups(user).get(0));
> }
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (YARN-10198) [managedParent].%primary_group mapping rule doesn't work after YARN-9868
[
https://issues.apache.org/jira/browse/YARN-10198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17060683#comment-17060683
]
Akhil PB edited comment on YARN-10198 at 3/17/20, 7:29 AM:
---
Expected behavior:
# *[managedParent].%primary_group*
** Should not create queue named *%primary_group* under *[managedParent]* if
leaf queue named *%primary_group* already exists.
** Should create new child queue under *[managedParent]* if leaf queue named
*%primary_group* does not exists.
# *[managedParent].%secondary_group*
** Should not create queue named *%secondary_group* under *[managedParent]* if
leaf queue named *%secondary_group* already exists.
** Should create new child queue under *[managedParent]* if leaf queue named
*%secondary_group* does not exists.
Note that for current static mappings like *u:%user:%primary_group* and
*u:%user:%secondary_group*, following is the behavior and works as expected.
# *u:%user:%primary_group*
** App submitted when leaf queue named *%primary_group*( is present
** App failed when leaf queue named *%primary_group* is not present or stopped
# *u:%user:%secondary_group*
** App submitted when leaf queue named *%secondary_group* is present
** App submitted to "default" queue when leaf queue named *%secondary_group* is
not present
Please share your thoughts if I am missing something.
cc: [~sunilg] [~prabhujoseph] [~pbacsko]
was (Author: akhilpb):
Expected behavior:
# *[managedParent].%primary_group*
** Should not create queue name *%primary_group* under *[managedParent]* if
leaf queue named *%primary_group* already exists.
** Should create new child queue under *[managedParent]* if leaf queue named
*%primary_group* does not exists.
# *[managedParent].%secondary_group*
** Should not create queue name *%secondary_group* under *[managedParent]* if
leaf queue named *%secondary_group* already exists.
** Should create new child queue under *[managedParent]* if leaf queue named
*%secondary_group* does not exists.
Note that for current static mappings like *u:%user:%primary_group* and
*u:%user:%secondary_group*, following is the behavior and works as expected.
# *u:%user:%primary_group*
** App submitted when leaf queue named *%primary_group*( is present
** App failed when leaf queue named *%primary_group* is not present or stopped
# *u:%user:%secondary_group*
** App submitted when leaf queue named *%secondary_group* is present
** App submitted to "default" queue when leaf queue named *%secondary_group* is
not present
Please share your thoughts if I am missing something.
cc: [~sunilg] [~prabhujoseph] [~pbacsko]
> [managedParent].%primary_group mapping rule doesn't work after YARN-9868
>
>
> Key: YARN-10198
> URL: https://issues.apache.org/jira/browse/YARN-10198
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacity scheduler
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
>
> YARN-9868 introduced an unnecessary check if we have the following placement
> rule:
> [managedParentQueue].%primary_group
> Here, {{%primary_group}} is expected to be created if it doesn't exist.
> However, there is this validation code which is not necessary:
> {noformat}
> } else if (mapping.getQueue().equals(PRIMARY_GROUP_MAPPING)) {
> if (this.queueManager
> .getQueue(groups.getGroups(user).get(0)) != null) {
> return getPlacementContext(mapping,
> groups.getGroups(user).get(0));
> } else {
> return null;
> }
> {noformat}
> We should revert this part to the original version:
> {noformat}
> } else if (mapping.queue.equals(PRIMARY_GROUP_MAPPING)) {
> return getPlacementContext(mapping,
> groups.getGroups(user).get(0));
> }
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (YARN-10198) [managedParent].%primary_group mapping rule doesn't work after YARN-9868
[
https://issues.apache.org/jira/browse/YARN-10198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17060683#comment-17060683
]
Akhil PB edited comment on YARN-10198 at 3/17/20, 7:29 AM:
---
Expected behavior:
# *[managedParent].%primary_group*
** Should not create queue named *%primary_group* under *[managedParent]* if
leaf queue named *%primary_group* already exists.
** Should create new child queue under *[managedParent]* if leaf queue named
*%primary_group* does not exists.
# *[managedParent].%secondary_group*
** Should not create queue named *%secondary_group* under *[managedParent]* if
leaf queue named *%secondary_group* already exists.
** Should create new child queue under *[managedParent]* if leaf queue named
*%secondary_group* does not exists.
Note that for current static mappings like *u:%user:%primary_group* and
*u:%user:%secondary_group*, following is the behavior and works as expected.
# *u:%user:%primary_group*
** App submitted when leaf queue named *%primary_group* is present
** App failed when leaf queue named *%primary_group* is not present or stopped
# *u:%user:%secondary_group*
** App submitted when leaf queue named *%secondary_group* is present
** App submitted to "default" queue when leaf queue named *%secondary_group* is
not present
Please share your thoughts if I am missing something.
cc: [~sunilg] [~prabhujoseph] [~pbacsko]
was (Author: akhilpb):
Expected behavior:
# *[managedParent].%primary_group*
** Should not create queue named *%primary_group* under *[managedParent]* if
leaf queue named *%primary_group* already exists.
** Should create new child queue under *[managedParent]* if leaf queue named
*%primary_group* does not exists.
# *[managedParent].%secondary_group*
** Should not create queue named *%secondary_group* under *[managedParent]* if
leaf queue named *%secondary_group* already exists.
** Should create new child queue under *[managedParent]* if leaf queue named
*%secondary_group* does not exists.
Note that for current static mappings like *u:%user:%primary_group* and
*u:%user:%secondary_group*, following is the behavior and works as expected.
# *u:%user:%primary_group*
** App submitted when leaf queue named *%primary_group*( is present
** App failed when leaf queue named *%primary_group* is not present or stopped
# *u:%user:%secondary_group*
** App submitted when leaf queue named *%secondary_group* is present
** App submitted to "default" queue when leaf queue named *%secondary_group* is
not present
Please share your thoughts if I am missing something.
cc: [~sunilg] [~prabhujoseph] [~pbacsko]
> [managedParent].%primary_group mapping rule doesn't work after YARN-9868
>
>
> Key: YARN-10198
> URL: https://issues.apache.org/jira/browse/YARN-10198
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacity scheduler
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
>
> YARN-9868 introduced an unnecessary check if we have the following placement
> rule:
> [managedParentQueue].%primary_group
> Here, {{%primary_group}} is expected to be created if it doesn't exist.
> However, there is this validation code which is not necessary:
> {noformat}
> } else if (mapping.getQueue().equals(PRIMARY_GROUP_MAPPING)) {
> if (this.queueManager
> .getQueue(groups.getGroups(user).get(0)) != null) {
> return getPlacementContext(mapping,
> groups.getGroups(user).get(0));
> } else {
> return null;
> }
> {noformat}
> We should revert this part to the original version:
> {noformat}
> } else if (mapping.queue.equals(PRIMARY_GROUP_MAPPING)) {
> return getPlacementContext(mapping,
> groups.getGroups(user).get(0));
> }
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10198) [managedParent].%primary_group mapping rule doesn't work after YARN-9868
[
https://issues.apache.org/jira/browse/YARN-10198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17060683#comment-17060683
]
Akhil PB commented on YARN-10198:
-
Expected behavior:
# *[managedParent].%primary_group*
** Should not create queue name *%primary_group* under *[managedParent]* if
leaf queue named *%primary_group* already exists.
** Should create new child queue under *[managedParent]* if leaf queue named
*%primary_group* does not exists.
# *[managedParent].%secondary_group*
** Should not create queue name *%secondary_group* under *[managedParent]* if
leaf queue named *%secondary_group* already exists.
** Should create new child queue under *[managedParent]* if leaf queue named
*%secondary_group* does not exists.
Note that for current static mappings like *u:%user:%primary_group* and
*u:%user:%secondary_group*, following is the behavior and works as expected.
# *u:%user:%primary_group*
** App submitted when leaf queue named *%primary_group*( is present
** App failed when leaf queue named *%primary_group* is not present or stopped
# *u:%user:%secondary_group*
** App submitted when leaf queue named *%secondary_group* is present
** App submitted to "default" queue when leaf queue named *%secondary_group* is
not present
Please share your thoughts if I am missing something.
cc: [~sunilg] [~prabhujoseph] [~pbacsko]
> [managedParent].%primary_group mapping rule doesn't work after YARN-9868
>
>
> Key: YARN-10198
> URL: https://issues.apache.org/jira/browse/YARN-10198
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacity scheduler
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
>
> YARN-9868 introduced an unnecessary check if we have the following placement
> rule:
> [managedParentQueue].%primary_group
> Here, {{%primary_group}} is expected to be created if it doesn't exist.
> However, there is this validation code which is not necessary:
> {noformat}
> } else if (mapping.getQueue().equals(PRIMARY_GROUP_MAPPING)) {
> if (this.queueManager
> .getQueue(groups.getGroups(user).get(0)) != null) {
> return getPlacementContext(mapping,
> groups.getGroups(user).get(0));
> } else {
> return null;
> }
> {noformat}
> We should revert this part to the original version:
> {noformat}
> } else if (mapping.queue.equals(PRIMARY_GROUP_MAPPING)) {
> return getPlacementContext(mapping,
> groups.getGroups(user).get(0));
> }
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10069) Showing jstack on UI for containers
[ https://issues.apache.org/jira/browse/YARN-10069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17009392#comment-17009392 ] Akhil PB commented on YARN-10069: - [~cane] is this jira for showing stack trace for the failed container in UI2? > Showing jstack on UI for containers > --- > > Key: YARN-10069 > URL: https://issues.apache.org/jira/browse/YARN-10069 > Project: Hadoop YARN > Issue Type: Improvement > Components: nodemanager >Reporter: zhoukang >Assignee: zhoukang >Priority: Major > > In this jira, i want to post a patch to support showing jstack on the > container ui -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10020) Fix build instruction of hadoop-yarn-ui
[ https://issues.apache.org/jira/browse/YARN-10020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16991237#comment-16991237 ] Akhil PB commented on YARN-10020: - [~iwasakims] The prerequisites mentioned in the README.md is for local development. In case of hadoop release builds, frontend-maven-plugin will be used. Usually we are not using maven for local dev, we will be running ember dev server running locally (hence yarn and bower). cc: [~sunilg] > Fix build instruction of hadoop-yarn-ui > --- > > Key: YARN-10020 > URL: https://issues.apache.org/jira/browse/YARN-10020 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Masatake Iwasaki >Assignee: Masatake Iwasaki >Priority: Minor > > We don't need to manually install package managers such as yarn and bower as > described in README.md since frontend-maven-plugin was introduced by > YARN-6278. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-9729) [UI2] Fix error message for logs without ATSv2
[
https://issues.apache.org/jira/browse/YARN-9729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16903768#comment-16903768
]
Akhil PB commented on YARN-9729:
[~zsiegl] Could you please use follow code snippet in {{isTimelineUnHealthy}}
if block in logs.hbs file.
{noformat}
Logs are unavailable because Application Timeline Service seems
unhealthy.
{noformat}
The above code will produce !Screenshot 2019-08-09 at 3.22.19 PM.png!
cc: [~sunilg]
> [UI2] Fix error message for logs without ATSv2
> --
>
> Key: YARN-9729
> URL: https://issues.apache.org/jira/browse/YARN-9729
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: yarn-ui-v2
>Affects Versions: 3.2.0, 3.1.2
>Reporter: Zoltan Siegl
>Assignee: Zoltan Siegl
>Priority: Major
> Attachments: ATS_NOT_UP.png, ATS_UP_WITH_NO_LOGS.png, Screenshot
> 2019-08-08 at 13.23.11.png, Screenshot 2019-08-08 at 13.23.21.png, Screenshot
> 2019-08-09 at 3.22.19 PM.png, YARN-9729.001.patch, after_patch.png
>
>
> On UI2 applications page logs are not available unless ATSv2 is running. The
> reason for logs not to appear is unclarified on the UI.
> When ATS is reported to be unhealthy, a descriptive error message should
> appear.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9729) [UI2] Fix error message for logs without ATSv2
[ https://issues.apache.org/jira/browse/YARN-9729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-9729: --- Attachment: Screenshot 2019-08-09 at 3.22.19 PM.png > [UI2] Fix error message for logs without ATSv2 > -- > > Key: YARN-9729 > URL: https://issues.apache.org/jira/browse/YARN-9729 > Project: Hadoop YARN > Issue Type: Improvement > Components: yarn-ui-v2 >Affects Versions: 3.2.0, 3.1.2 >Reporter: Zoltan Siegl >Assignee: Zoltan Siegl >Priority: Major > Attachments: ATS_NOT_UP.png, ATS_UP_WITH_NO_LOGS.png, Screenshot > 2019-08-08 at 13.23.11.png, Screenshot 2019-08-08 at 13.23.21.png, Screenshot > 2019-08-09 at 3.22.19 PM.png, YARN-9729.001.patch, after_patch.png > > > On UI2 applications page logs are not available unless ATSv2 is running. The > reason for logs not to appear is unclarified on the UI. > When ATS is reported to be unhealthy, a descriptive error message should > appear. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-9715) [YARN UI2] yarn-container-log support for https Knox Gateway url in nodes page
[ https://issues.apache.org/jira/browse/YARN-9715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16903581#comment-16903581 ] Akhil PB commented on YARN-9715: Uploaded rebased v2 patch > [YARN UI2] yarn-container-log support for https Knox Gateway url in nodes page > -- > > Key: YARN-9715 > URL: https://issues.apache.org/jira/browse/YARN-9715 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Prabhu Joseph >Assignee: Akhil PB >Priority: Major > Attachments: Screen Shot 2019-08-08 at 12.54.40 PM.png, Screen Shot > 2019-08-08 at 12.55.03 PM.png, Screen Shot 2019-08-08 at 2.51.46 PM.png, > Screen Shot 2019-08-08 at 3.03.16 PM.png, YARN-9715.001.patch, > YARN-9715.002.patch > > > Currently yarn-container-log (UI2 - Nodes - List of Containers - log file) > creates url with node scheme (http) and nodeHttpAddress. This does not work > with Knox Gateway https url. The logic to construct url can be improved to > accept both normal and knox case. The similar way is used in Applications -> > Logs Section. > And also UI2 - Nodes - List of Containers - log file does not have pagination > support for log file. > > *Screenshot of Problematic Page *: Knox Url - UI2 - Nodes - List of > Containers - log file > !Screen Shot 2019-08-08 at 3.03.16 PM.png|height=200|width=350! > > -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9715) [YARN UI2] yarn-container-log support for https Knox Gateway url in nodes page
[ https://issues.apache.org/jira/browse/YARN-9715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-9715: --- Attachment: YARN-9715.002.patch > [YARN UI2] yarn-container-log support for https Knox Gateway url in nodes page > -- > > Key: YARN-9715 > URL: https://issues.apache.org/jira/browse/YARN-9715 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Prabhu Joseph >Assignee: Akhil PB >Priority: Major > Attachments: Screen Shot 2019-08-08 at 12.54.40 PM.png, Screen Shot > 2019-08-08 at 12.55.03 PM.png, Screen Shot 2019-08-08 at 2.51.46 PM.png, > Screen Shot 2019-08-08 at 3.03.16 PM.png, YARN-9715.001.patch, > YARN-9715.002.patch > > > Currently yarn-container-log (UI2 - Nodes - List of Containers - log file) > creates url with node scheme (http) and nodeHttpAddress. This does not work > with Knox Gateway https url. The logic to construct url can be improved to > accept both normal and knox case. The similar way is used in Applications -> > Logs Section. > And also UI2 - Nodes - List of Containers - log file does not have pagination > support for log file. > > *Screenshot of Problematic Page *: Knox Url - UI2 - Nodes - List of > Containers - log file > !Screen Shot 2019-08-08 at 3.03.16 PM.png|height=200|width=350! > > -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9715) [YARN UI2] yarn-container-log support for https Knox Gateway url in nodes page
[ https://issues.apache.org/jira/browse/YARN-9715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-9715: --- Attachment: (was: YARN-9715.001.patch) > [YARN UI2] yarn-container-log support for https Knox Gateway url in nodes page > -- > > Key: YARN-9715 > URL: https://issues.apache.org/jira/browse/YARN-9715 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Prabhu Joseph >Assignee: Akhil PB >Priority: Major > Attachments: Screen Shot 2019-08-08 at 12.54.40 PM.png, Screen Shot > 2019-08-08 at 12.55.03 PM.png, YARN-9715.001.patch > > > Currently yarn-container-log (UI2 - Nodes - List of Containers - log file) > creates url with node scheme (http) and nodeHttpAddress. This does not work > with Knox Gateway https url. The logic to construct url can be improved to > accept both normal and knox case. The similar way is used in Applications -> > Logs Section. > And also UI2 - Nodes - List of Containers - log file does not have pagination > support for log file. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9715) [YARN UI2] yarn-container-log support for https Knox Gateway url in nodes page
[ https://issues.apache.org/jira/browse/YARN-9715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-9715: --- Attachment: YARN-9715.001.patch > [YARN UI2] yarn-container-log support for https Knox Gateway url in nodes page > -- > > Key: YARN-9715 > URL: https://issues.apache.org/jira/browse/YARN-9715 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Prabhu Joseph >Assignee: Akhil PB >Priority: Major > Attachments: Screen Shot 2019-08-08 at 12.54.40 PM.png, Screen Shot > 2019-08-08 at 12.55.03 PM.png, YARN-9715.001.patch > > > Currently yarn-container-log (UI2 - Nodes - List of Containers - log file) > creates url with node scheme (http) and nodeHttpAddress. This does not work > with Knox Gateway https url. The logic to construct url can be improved to > accept both normal and knox case. The similar way is used in Applications -> > Logs Section. > And also UI2 - Nodes - List of Containers - log file does not have pagination > support for log file. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9715) [YARN UI2] yarn-container-log support for https Knox Gateway url in nodes page
[ https://issues.apache.org/jira/browse/YARN-9715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-9715: --- Attachment: (was: YARN-9715.001.patch) > [YARN UI2] yarn-container-log support for https Knox Gateway url in nodes page > -- > > Key: YARN-9715 > URL: https://issues.apache.org/jira/browse/YARN-9715 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Prabhu Joseph >Assignee: Akhil PB >Priority: Major > Attachments: Screen Shot 2019-08-08 at 12.54.40 PM.png, Screen Shot > 2019-08-08 at 12.55.03 PM.png, YARN-9715.001.patch > > > Currently yarn-container-log (UI2 - Nodes - List of Containers - log file) > creates url with node scheme (http) and nodeHttpAddress. This does not work > with Knox Gateway https url. The logic to construct url can be improved to > accept both normal and knox case. The similar way is used in Applications -> > Logs Section. > And also UI2 - Nodes - List of Containers - log file does not have pagination > support for log file. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9715) [YARN UI2] yarn-container-log support for https Knox Gateway url in nodes page
[ https://issues.apache.org/jira/browse/YARN-9715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-9715: --- Attachment: YARN-9715.001.patch > [YARN UI2] yarn-container-log support for https Knox Gateway url in nodes page > -- > > Key: YARN-9715 > URL: https://issues.apache.org/jira/browse/YARN-9715 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Prabhu Joseph >Assignee: Akhil PB >Priority: Major > Attachments: Screen Shot 2019-08-08 at 12.54.40 PM.png, Screen Shot > 2019-08-08 at 12.55.03 PM.png, YARN-9715.001.patch > > > Currently yarn-container-log (UI2 - Nodes - List of Containers - log file) > creates url with node scheme (http) and nodeHttpAddress. This does not work > with Knox Gateway https url. The logic to construct url can be improved to > accept both normal and knox case. The similar way is used in Applications -> > Logs Section. > And also UI2 - Nodes - List of Containers - log file does not have pagination > support for log file. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Assigned] (YARN-9725) [YARN UI2] Running Containers Logs from NM Local Dir are not shown in Applications - Logs Section
[
https://issues.apache.org/jira/browse/YARN-9725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akhil PB reassigned YARN-9725:
--
Assignee: Akhil PB
> [YARN UI2] Running Containers Logs from NM Local Dir are not shown in
> Applications - Logs Section
> -
>
> Key: YARN-9725
> URL: https://issues.apache.org/jira/browse/YARN-9725
> Project: Hadoop YARN
> Issue Type: Bug
> Components: yarn-ui-v2
>Affects Versions: 3.2.0
>Reporter: Prabhu Joseph
>Assignee: Akhil PB
>Priority: Major
> Attachments: NM_Local_Dir.png, Running_Container2_UI.png,
> Running_Container_Log_Dir.png, Running_Container_Logs.png, YARN_UI_V1.png
>
>
> [YARN UI2] Running Containers Logs from NM Local Dir are not shown in
> Applications - Logs Section. It shows only the aggregated log files for that
> container and does not show the log files which are present under NM Local
> Dir. YARN UI V1 was showing the log files from NM local dir.
> On Analysis found, UI2 calls AHSWebServices /containers/{containerid}/logs
> without nm.id and so AHSWebServices does not fetch from NodeManager
> WebServices, it fetches only from Aggregated App Log Dir.
> {color:#14892c}*UI2 Shows Only Aggregated Logs*{color}
> !Running_Container_Logs.png|height=200!
> {color:#14892c}*NM Local Dir Logs which are not shown*{color}
> !NM_Local_Dir.png|height=200!
> {color:#14892c}*UI1 Shown local dir logs*{color}
> !YARN_UI_V1.png|height=200!
> {color:#14892c}*UI2 does not show log for Container_2*{color}
> !Running_Container2_UI.png|height=200!
> {color:#14892c}*Container_2 has logs under NM Local Dir*{color}
> !Running_Container_Log_Dir.png|height=200!
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9715) [YARN UI2] yarn-container-log support for https Knox Gateway url in nodes page
[ https://issues.apache.org/jira/browse/YARN-9715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-9715: --- Attachment: YARN-9715.001.patch > [YARN UI2] yarn-container-log support for https Knox Gateway url in nodes page > -- > > Key: YARN-9715 > URL: https://issues.apache.org/jira/browse/YARN-9715 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Prabhu Joseph >Assignee: Akhil PB >Priority: Major > Attachments: Screen Shot 2019-08-08 at 12.54.40 PM.png, Screen Shot > 2019-08-08 at 12.55.03 PM.png, YARN-9715.001.patch > > > Currently yarn-container-log (UI2 - Nodes - List of Containers - log file) > creates url with node scheme (http) and nodeHttpAddress. This does not work > with Knox Gateway https url. The logic to construct url can be improved to > accept both normal and knox case. The similar way is used in Applications -> > Logs Section. > And also UI2 - Nodes - List of Containers - log file does not have pagination > support for log file. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9715) [YARN UI2] yarn-container-log support for https Knox Gateway url in nodes page
[ https://issues.apache.org/jira/browse/YARN-9715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-9715: --- Attachment: (was: YARN-9715.001.patch) > [YARN UI2] yarn-container-log support for https Knox Gateway url in nodes page > -- > > Key: YARN-9715 > URL: https://issues.apache.org/jira/browse/YARN-9715 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Prabhu Joseph >Assignee: Akhil PB >Priority: Major > Attachments: Screen Shot 2019-08-08 at 12.54.40 PM.png, Screen Shot > 2019-08-08 at 12.55.03 PM.png, YARN-9715.001.patch > > > Currently yarn-container-log (UI2 - Nodes - List of Containers - log file) > creates url with node scheme (http) and nodeHttpAddress. This does not work > with Knox Gateway https url. The logic to construct url can be improved to > accept both normal and knox case. The similar way is used in Applications -> > Logs Section. > And also UI2 - Nodes - List of Containers - log file does not have pagination > support for log file. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-9715) [YARN UI2] yarn-container-log support for https Knox Gateway url in nodes page
[ https://issues.apache.org/jira/browse/YARN-9715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16902741#comment-16902741 ] Akhil PB commented on YARN-9715: Attached v1 patch. [~sunilg] [~Prabhu Joseph] Please help to verify and commit the patch. > [YARN UI2] yarn-container-log support for https Knox Gateway url in nodes page > -- > > Key: YARN-9715 > URL: https://issues.apache.org/jira/browse/YARN-9715 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Prabhu Joseph >Assignee: Akhil PB >Priority: Major > Attachments: YARN-9715.001.patch > > > Currently yarn-container-log (UI2 - Nodes - List of Containers - log file) > creates url with node scheme (http) and nodeHttpAddress. This does not work > with Knox Gateway https url. The logic to construct url can be improved to > accept both normal and knox case. The similar way is used in Applications -> > Logs Section. > And also UI2 - Nodes - List of Containers - log file does not have pagination > support for log file. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9715) [YARN UI2] yarn-container-log support for https Knox Gateway url in nodes page
[ https://issues.apache.org/jira/browse/YARN-9715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-9715: --- Attachment: YARN-9715.001.patch > [YARN UI2] yarn-container-log support for https Knox Gateway url in nodes page > -- > > Key: YARN-9715 > URL: https://issues.apache.org/jira/browse/YARN-9715 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Prabhu Joseph >Assignee: Akhil PB >Priority: Major > Attachments: YARN-9715.001.patch > > > Currently yarn-container-log (UI2 - Nodes - List of Containers - log file) > creates url with node scheme (http) and nodeHttpAddress. This does not work > with Knox Gateway https url. The logic to construct url can be improved to > accept both normal and knox case. The similar way is used in Applications -> > Logs Section. > And also UI2 - Nodes - List of Containers - log file does not have pagination > support for log file. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9726) [YARN UI2] Implement server side pagination for logs in application, service and nodes pages
[ https://issues.apache.org/jira/browse/YARN-9726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-9726: --- Description: Currently in application and service logs pages, logs are shown using client side pagging. This would make page to render slow if log size is very high. Similarly there is no logs pagging implemented in nodes page. Solution: Show last 4 bytes of logs initially. Then show full logs based on user input. was:Currently in application and service logs pages, logs are shown using client side pagging. This would make page to render slow if log size is very high. Similarly there is no logs pagging implemented in nodes page. > [YARN UI2] Implement server side pagination for logs in application, service > and nodes pages > > > Key: YARN-9726 > URL: https://issues.apache.org/jira/browse/YARN-9726 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Major > > Currently in application and service logs pages, logs are shown using client > side pagging. This would make page to render slow if log size is very high. > Similarly there is no logs pagging implemented in nodes page. > Solution: Show last 4 bytes of logs initially. Then show full logs based on > user input. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9726) [YARN UI2] Implement server side pagination for logs in application, service and nodes pages
[ https://issues.apache.org/jira/browse/YARN-9726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-9726: --- Summary: [YARN UI2] Implement server side pagination for logs in application, service and nodes pages (was: [YARN UI2] Implement server side pagination for logs in application/service and nodes pages) > [YARN UI2] Implement server side pagination for logs in application, service > and nodes pages > > > Key: YARN-9726 > URL: https://issues.apache.org/jira/browse/YARN-9726 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Major > > Currently in application and service logs pages, logs are shown using client > side pagging. This would make page to render slow if log size is very high. > Similarly there is no logs pagging implemented in nodes page. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-9726) [YARN UI2] Implement server side pagging in logs in application/service and nodes pages
Akhil PB created YARN-9726: -- Summary: [YARN UI2] Implement server side pagging in logs in application/service and nodes pages Key: YARN-9726 URL: https://issues.apache.org/jira/browse/YARN-9726 Project: Hadoop YARN Issue Type: Improvement Reporter: Akhil PB Assignee: Akhil PB Currently in application and service logs pages, logs are shown using client side pagging. This would make page to render slow if log size is very high. Similarly there is no logs pagging implemented in nodes page. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9726) [YARN UI2] Implement server side pagination for logs in application/service and nodes pages
[ https://issues.apache.org/jira/browse/YARN-9726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-9726: --- Summary: [YARN UI2] Implement server side pagination for logs in application/service and nodes pages (was: [YARN UI2] Implement server side pagging in logs in application/service and nodes pages) > [YARN UI2] Implement server side pagination for logs in application/service > and nodes pages > --- > > Key: YARN-9726 > URL: https://issues.apache.org/jira/browse/YARN-9726 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Major > > Currently in application and service logs pages, logs are shown using client > side pagging. This would make page to render slow if log size is very high. > Similarly there is no logs pagging implemented in nodes page. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9715) [YARN UI2] yarn-container-log support for https Knox Gateway url in nodes page
[ https://issues.apache.org/jira/browse/YARN-9715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-9715: --- Summary: [YARN UI2] yarn-container-log support for https Knox Gateway url in nodes page (was: YARN UI2 - yarn-container-log support for https Knox Gateway url) > [YARN UI2] yarn-container-log support for https Knox Gateway url in nodes page > -- > > Key: YARN-9715 > URL: https://issues.apache.org/jira/browse/YARN-9715 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Prabhu Joseph >Assignee: Akhil PB >Priority: Major > > Currently yarn-container-log (UI2 - Nodes - List of Containers - log file) > creates url with node scheme (http) and nodeHttpAddress. This does not work > with Knox Gateway https url. The logic to construct url can be improved to > accept both normal and knox case. The similar way is used in Applications -> > Logs Section. > And also UI2 - Nodes - List of Containers - log file does not have pagination > support for log file. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-9600) Support self-adaption width for columns of containers table on app attempt page
[ https://issues.apache.org/jira/browse/YARN-9600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16856369#comment-16856369 ] Akhil PB commented on YARN-9600: [~Tao Yang] LGTM. +1 for the patch. cc: [~cheersyang] > Support self-adaption width for columns of containers table on app attempt > page > --- > > Key: YARN-9600 > URL: https://issues.apache.org/jira/browse/YARN-9600 > Project: Hadoop YARN > Issue Type: Bug > Components: webapp >Reporter: Tao Yang >Assignee: Tao Yang >Priority: Minor > Attachments: YARN-9600.001.patch, image-2019-06-04-16-45-49-359.png, > image-2019-06-04-16-55-18-899.png > > > When there are outstanding requests showing on app attempt page, the page > will be automatically stretched horizontally, after that, columns of > containers table can't fill the table and left two blank spaces in the > leftmost and the rightmost of this table, as the following picture shows: > !image-2019-06-04-16-45-49-359.png|width=647,height=231! > We can add relative width style (width:100%) for containers table to make > columns self-adaption. > After doing that containers table show as follows: > !image-2019-06-04-16-55-18-899.png|width=645,height=229! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-9543) UI2 should handle missing ATSv2 gracefully
[ https://issues.apache.org/jira/browse/YARN-9543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16846580#comment-16846580 ] Akhil PB commented on YARN-9543: Hi [~snemeth] I uploaded the v2 patch. [~sunilg] could you pls take a look at the patch. > UI2 should handle missing ATSv2 gracefully > -- > > Key: YARN-9543 > URL: https://issues.apache.org/jira/browse/YARN-9543 > Project: Hadoop YARN > Issue Type: Improvement > Components: ATSv2, yarn-ui-v2 >Affects Versions: 3.1.2 >Reporter: Zoltan Siegl >Assignee: Zoltan Siegl >Priority: Major > Attachments: YARN-9543.001.patch, YARN-9543.002.patch > > > Resource manager UI2 is throwing some console errors and an error page on the > flows page. > Suggested improvements: > * Disable or remove the flows tab if ATSv2 is not available or not installed > * Handle all connection errors to ATSv2 gracefully -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (YARN-9543) UI2 should handle missing ATSv2 gracefully
[ https://issues.apache.org/jira/browse/YARN-9543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16846098#comment-16846098 ] Akhil PB edited comment on YARN-9543 at 5/22/19 6:59 PM: - Hi [~snemeth] The function urlForQueryRecord is Emberjs adapter thing. was (Author: akhilpb): Hi [~snemeth] The function urlForQueryRecord is related to Emberjs adapter. > UI2 should handle missing ATSv2 gracefully > -- > > Key: YARN-9543 > URL: https://issues.apache.org/jira/browse/YARN-9543 > Project: Hadoop YARN > Issue Type: Improvement > Components: ATSv2, yarn-ui-v2 >Affects Versions: 3.1.2 >Reporter: Zoltan Siegl >Assignee: Zoltan Siegl >Priority: Major > Attachments: YARN-9543.001.patch, YARN-9543.002.patch > > > Resource manager UI2 is throwing some console errors and an error page on the > flows page. > Suggested improvements: > * Disable or remove the flows tab if ATSv2 is not available or not installed > * Handle all connection errors to ATSv2 gracefully -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-9543) UI2 should handle missing ATSv2 gracefully
[ https://issues.apache.org/jira/browse/YARN-9543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16846098#comment-16846098 ] Akhil PB commented on YARN-9543: Hi [~snemeth] The function urlForQueryRecord is related to Emberjs adapter. > UI2 should handle missing ATSv2 gracefully > -- > > Key: YARN-9543 > URL: https://issues.apache.org/jira/browse/YARN-9543 > Project: Hadoop YARN > Issue Type: Improvement > Components: ATSv2, yarn-ui-v2 >Affects Versions: 3.1.2 >Reporter: Zoltan Siegl >Assignee: Zoltan Siegl >Priority: Major > Attachments: YARN-9543.001.patch, YARN-9543.002.patch > > > Resource manager UI2 is throwing some console errors and an error page on the > flows page. > Suggested improvements: > * Disable or remove the flows tab if ATSv2 is not available or not installed > * Handle all connection errors to ATSv2 gracefully -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-9543) UI2 should handle missing ATSv2 gracefully
[ https://issues.apache.org/jira/browse/YARN-9543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1684#comment-1684 ] Akhil PB commented on YARN-9543: Uploaded v2 patch. cc: [~sunilg] [~wangda] [~zsiegl] > UI2 should handle missing ATSv2 gracefully > -- > > Key: YARN-9543 > URL: https://issues.apache.org/jira/browse/YARN-9543 > Project: Hadoop YARN > Issue Type: Improvement > Components: ATSv2, yarn-ui-v2 >Affects Versions: 3.1.2 >Reporter: Zoltan Siegl >Assignee: Zoltan Siegl >Priority: Major > Attachments: YARN-9543.001.patch, YARN-9543.002.patch > > > Resource manager UI2 is throwing some console errors and a error page on > flows page. > Suggested improvements: > * Disable or remove flows tab if ATSv2 is not available/installed > * Handle all connection errors to ATSv2 gracefully -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9543) UI2 should handle missing ATSv2 gracefully
[ https://issues.apache.org/jira/browse/YARN-9543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-9543: --- Attachment: YARN-9543.002.patch > UI2 should handle missing ATSv2 gracefully > -- > > Key: YARN-9543 > URL: https://issues.apache.org/jira/browse/YARN-9543 > Project: Hadoop YARN > Issue Type: Improvement > Components: ATSv2, yarn-ui-v2 >Affects Versions: 3.1.2 >Reporter: Zoltan Siegl >Assignee: Zoltan Siegl >Priority: Major > Attachments: YARN-9543.001.patch, YARN-9543.002.patch > > > Resource manager UI2 is throwing some console errors and a error page on > flows page. > Suggested improvements: > * Disable or remove flows tab if ATSv2 is not available/installed > * Handle all connection errors to ATSv2 gracefully -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-9567) Add diagnostics for outstanding resource requests on app attempts page
[ https://issues.apache.org/jira/browse/YARN-9567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16844563#comment-16844563 ] Akhil PB commented on YARN-9567: Created a UI2 ticket for the same. YARN-9572 cc: [~wangda] [~sunilg] > Add diagnostics for outstanding resource requests on app attempts page > -- > > Key: YARN-9567 > URL: https://issues.apache.org/jira/browse/YARN-9567 > Project: Hadoop YARN > Issue Type: Sub-task > Components: capacityscheduler >Reporter: Tao Yang >Assignee: Tao Yang >Priority: Major > Attachments: no_diagnostic_at_first.png, > show_diagnostics_after_requesting_app_activities_REST_API.png > > > Currently on app attempt page we can see outstanding resource requests, it > will be helpful for users to know why if we can join diagnostics of this app > with these. > Discussed with [~cheersyang], we can passively load diagnostics from cache of > completed app activities instead of actively triggering which may bring > uncontrollable risks. > For example: > (1) At first we can see no diagnostic in cache if app activities not > triggered below the outstanding requests. > !no_diagnostic_at_first.png|width=793,height=248! > (2) After requesting the application activities REST API, we can see > diagnostics now. > !show_diagnostics_after_requesting_app_activities_REST_API.png|width=1046,height=276! > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-9572) [UI2] Add diagnostics for outstanding resource requests on app attempts page
Akhil PB created YARN-9572: -- Summary: [UI2] Add diagnostics for outstanding resource requests on app attempts page Key: YARN-9572 URL: https://issues.apache.org/jira/browse/YARN-9572 Project: Hadoop YARN Issue Type: Improvement Components: yarn-ui-v2 Reporter: Akhil PB -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-8947) [UI2] Active User info missing from UI2
[ https://issues.apache.org/jira/browse/YARN-8947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-8947: --- Attachment: YARN-8947.004.patch > [UI2] Active User info missing from UI2 > --- > > Key: YARN-8947 > URL: https://issues.apache.org/jira/browse/YARN-8947 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Major > Attachments: Active_User_Info_RM_UI1.png, > Active_User_Info_RM_UI2_Fixed.png, Active_User_Info_RM_UI2_Fixed_2.png, > YARN-8947.001.patch, YARN-8947.002.patch, YARN-8947.003.patch, > YARN-8947.004.patch > > > UI1 Scheduler section has Active User info. Where it shows Active users and > Application scheduled. > UI2 is missing that information. There is no way to get a summary of apps as > per User. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-8906) [UI2] NM hostnames not displayed correctly in Node Heatmap Chart
[ https://issues.apache.org/jira/browse/YARN-8906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-8906: --- Attachment: YARN-8906.002.patch > [UI2] NM hostnames not displayed correctly in Node Heatmap Chart > > > Key: YARN-8906 > URL: https://issues.apache.org/jira/browse/YARN-8906 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Charan Hebri >Assignee: Akhil PB >Priority: Major > Attachments: Node_Heatmap_Chart.png, Node_Heatmap_Chart_Fixed.png, > YARN-8906.001.patch, YARN-8906.002.patch > > > Hostnames displayed on the Node Heatmap Chart look garbled and are not > clearly visible. Attached screenshot. > cc [~akhilpb] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8906) [UI2] NM hostnames not displayed correctly in Node Heatmap Chart
[ https://issues.apache.org/jira/browse/YARN-8906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16784148#comment-16784148 ] Akhil PB commented on YARN-8906: trunk patch works for branch-3.1 and branch-3.2. cc [~sunilg] > [UI2] NM hostnames not displayed correctly in Node Heatmap Chart > > > Key: YARN-8906 > URL: https://issues.apache.org/jira/browse/YARN-8906 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Charan Hebri >Assignee: Akhil PB >Priority: Major > Attachments: Node_Heatmap_Chart.png, Node_Heatmap_Chart_Fixed.png, > YARN-8906.001.patch > > > Hostnames displayed on the Node Heatmap Chart look garbled and are not > clearly visible. Attached screenshot. > cc [~akhilpb] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8803) [UI2] Show flow runs in the order of recently created time in graph widgets
[ https://issues.apache.org/jira/browse/YARN-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16784144#comment-16784144 ] Akhil PB commented on YARN-8803: trunk patch works for branch-3.1 and branch-3.2. cc [~sunilg] > [UI2] Show flow runs in the order of recently created time in graph widgets > --- > > Key: YARN-8803 > URL: https://issues.apache.org/jira/browse/YARN-8803 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Major > Attachments: Screen Shot 2018-09-20 at 11.42.17 AM.png, Screen Shot > 2018-09-20 at 11.42.35 AM.png, Screen Shot 2018-09-20 at 11.42.46 AM.png, > YARN-8803.001.patch > > > Flow Run Vs Run Duration – shows Run1 a job where as Flow Run Vs Memory Used > shows Run 1 another job and the Table with list of Run Ids has all jobs in > different order sorted on Creation Time. The widgets will be useful if it is > representing the runs in same order as the Table so that easy to correlate. > Its better to have ordering in the widgets based on the creation time instead > of sorting based on time taken. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-8947) [UI2] Active User info missing from UI2
[ https://issues.apache.org/jira/browse/YARN-8947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-8947: --- Attachment: YARN-8947.003.patch > [UI2] Active User info missing from UI2 > --- > > Key: YARN-8947 > URL: https://issues.apache.org/jira/browse/YARN-8947 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Major > Attachments: Active_User_Info_RM_UI1.png, > Active_User_Info_RM_UI2_Fixed.png, YARN-8947.001.patch, YARN-8947.002.patch, > YARN-8947.003.patch > > > UI1 Scheduler section has Active User info. Where it shows Active users and > Application scheduled. > UI2 is missing that information. There is no way to get a summary of apps as > per User. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-8947) [UI2] Active User info missing from UI2
[ https://issues.apache.org/jira/browse/YARN-8947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-8947: --- Attachment: Active_User_Info_RM_UI2_Fixed_2.png > [UI2] Active User info missing from UI2 > --- > > Key: YARN-8947 > URL: https://issues.apache.org/jira/browse/YARN-8947 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Major > Attachments: Active_User_Info_RM_UI1.png, > Active_User_Info_RM_UI2_Fixed.png, Active_User_Info_RM_UI2_Fixed_2.png, > YARN-8947.001.patch, YARN-8947.002.patch, YARN-8947.003.patch > > > UI1 Scheduler section has Active User info. Where it shows Active users and > Application scheduled. > UI2 is missing that information. There is no way to get a summary of apps as > per User. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8947) [UI2] Active User info missing from UI2
[ https://issues.apache.org/jira/browse/YARN-8947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16776558#comment-16776558 ] Akhil PB commented on YARN-8947: [~sunilg] Could you pls review and commit the patch. trunk patch works for branch-3.2 and branch-3.1. See screenshot Active_User_Info_RM_UI2_Fixed.png for the UI fix. > [UI2] Active User info missing from UI2 > --- > > Key: YARN-8947 > URL: https://issues.apache.org/jira/browse/YARN-8947 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Major > Attachments: Active_User_Info_RM_UI1.png, > Active_User_Info_RM_UI2_Fixed.png, YARN-8947.001.patch, YARN-8947.002.patch > > > UI1 Scheduler section has Active User info. Where it shows Active users and > Application scheduled. > UI2 is missing that information. There is no way to get a summary of apps as > per User. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7824) [UI2] Yarn Component Instance page should include link to container logs
[ https://issues.apache.org/jira/browse/YARN-7824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16769086#comment-16769086 ] Akhil PB commented on YARN-7824: Attached branch-3.2 patch (works for branch-3.1 too). cc [~sunilg] > [UI2] Yarn Component Instance page should include link to container logs > > > Key: YARN-7824 > URL: https://issues.apache.org/jira/browse/YARN-7824 > Project: Hadoop YARN > Issue Type: Improvement > Components: yarn-ui-v2 >Affects Versions: 3.0.0 >Reporter: Yesha Vora >Assignee: Akhil PB >Priority: Major > Attachments: YARN-7824-branch-3.2.001.patch, YARN-7824.001.patch > > > Steps: > 1) Launch Httpd example > 2) Visit component Instance page for httpd-proxy-0 > This page has information regarding httpd-proxy-0 component. > This page should also include a link to container logs for this component > h2. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7824) [UI2] Yarn Component Instance page should include link to container logs
[ https://issues.apache.org/jira/browse/YARN-7824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-7824: --- Attachment: YARN-7824-branch-3.2.001.patch > [UI2] Yarn Component Instance page should include link to container logs > > > Key: YARN-7824 > URL: https://issues.apache.org/jira/browse/YARN-7824 > Project: Hadoop YARN > Issue Type: Improvement > Components: yarn-ui-v2 >Affects Versions: 3.0.0 >Reporter: Yesha Vora >Assignee: Akhil PB >Priority: Major > Attachments: YARN-7824-branch-3.2.001.patch, YARN-7824.001.patch > > > Steps: > 1) Launch Httpd example > 2) Visit component Instance page for httpd-proxy-0 > This page has information regarding httpd-proxy-0 component. > This page should also include a link to container logs for this component > h2. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9295) [UI2] Fix 'Decomissioned' label typo in Cluster Overview page
[ https://issues.apache.org/jira/browse/YARN-9295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-9295: --- Summary: [UI2] Fix 'Decomissioned' label typo in Cluster Overview page (was: Fix 'Decomissioned' label typo in Cluster Overview page) > [UI2] Fix 'Decomissioned' label typo in Cluster Overview page > - > > Key: YARN-9295 > URL: https://issues.apache.org/jira/browse/YARN-9295 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Charan Hebri >Assignee: Charan Hebri >Priority: Trivial > Attachments: Decommissioned-typo.png, YARN-9295.001.patch > > > Change label text from 'Decomissioned' to 'Decommissioned' in Node Managers > section of the Cluster Overview page. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-9240) YARN UI 2 footer shows the datetime in different timezone
[
https://issues.apache.org/jira/browse/YARN-9240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16756000#comment-16756000
]
Akhil PB commented on YARN-9240:
Hi [~masatana]
So YARN-8747 patch fixes the issue you mentioned above, right? Because I could
not figure out the moment-timezone fix version from the PR given above.
> YARN UI 2 footer shows the datetime in different timezone
> -
>
> Key: YARN-9240
> URL: https://issues.apache.org/jira/browse/YARN-9240
> Project: Hadoop YARN
> Issue Type: Bug
> Components: yarn-ui-v2
>Affects Versions: 3.2.0
> Environment: Windows 10/Firefox 64
> {code}
> (new Date()).toTimeString()
> => "09:11:16 GMT+0900 (日本標準時)"
> {code}
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Minor
>
> YARN Web UI 2 footer shows the started time about "2019-01-25 16:39" even if
> the ResourceManager started at "2019-01-26 00:39:34"(UTC), and my PC's
> localtime is JST.(+09:00 GMT)
> ResourceManager log is below: (Sever time is set as UTC).
> {code}
> 2019-01-26 00:39:34,619 INFO
> org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: STARTUP_MSG:
> /
> STARTUP_MSG: Starting ResourceManager
> STARTUP_MSG: host = X/X
> STARTUP_MSG: args = []
> STARTUP_MSG: version = 3.2.0
> (snip)
> {code}
> Web browser console outputs an error like below
> {code:java}
> TypeError: "c[0].match(...) is null"
> i http://localhost:8088/ui2/assets/vendor.js:5598:40973
> l http://localhost:8088/ui2/assets/vendor.js:5598:41338
> p http://localhost:8088/ui2/assets/vendor.js:5598:42035
> q http://localhost:8088/ui2/assets/vendor.js:5598:42235
> getDefaultTimezone http://localhost:8088/ui2/assets/yarn-ui.js:378:464
> convertTimestampWithTz
> http://localhost:8088/ui2/assets/yarn-ui.js:379:220
> timeStampToDate http://localhost:8088/ui2/assets/yarn-ui.js:360:80
> dateFormatter http://localhost:8088/ui2/assets/yarn-ui.js:177:1011
> compute http://localhost:8088/ui2/assets/vendor.js:1052:780
> value http://localhost:8088/ui2/assets/vendor.js:1528:12
> read http://localhost:8088/ui2/assets/vendor.js:1544:58
> readArray http://localhost:8088/ui2/assets/vendor.js:1545:110
> compute http://localhost:8088/ui2/assets/vendor.js:1553:317
> value http://localhost:8088/ui2/assets/vendor.js:1528:12
> read http://localhost:8088/ui2/assets/vendor.js:1544:58
> getValue http://localhost:8088/ui2/assets/vendor.js:907:329
> attribute http://localhost:8088/ui2/assets/vendor.js:2547:54
> attribute http://localhost:8088/ui2/assets/vendor.js:2575:623
> populateNodes http://localhost:8088/ui2/assets/vendor.js:2610:334
> render http://localhost:8088/ui2/assets/vendor.js:2605:265
> render http://localhost:8088/ui2/assets/vendor.js:2579:122
> yieldTemplate http://localhost:8088/ui2/assets/vendor.js:2479:155
> ifUnless http://localhost:8088/ui2/assets/vendor.js:871:85
> ifHelper http://localhost:8088/ui2/assets/vendor.js:869:524
> compute http://localhost:8088/ui2/assets/vendor.js:1051:500
> value http://localhost:8088/ui2/assets/vendor.js:1528:12
> invokeHelper http://localhost:8088/ui2/assets/vendor.js:914:14
> continueBlock http://localhost:8088/ui2/assets/vendor.js:2504:214
> renderAndCleanup http://localhost:8088/ui2/assets/vendor.js:2661:189
> hostBlock http://localhost:8088/ui2/assets/vendor.js:2505:150
> continueBlock http://localhost:8088/ui2/assets/vendor.js:2504:83
> block http://localhost:8088/ui2/assets/vendor.js:2503:1
> block http://localhost:8088/ui2/assets/vendor.js:2572:288
> populateNodes http://localhost:8088/ui2/assets/vendor.js:2610:34
> render http://localhost:8088/ui2/assets/vendor.js:2605:265
> render http://localhost:8088/ui2/assets/vendor.js:2579:122
> _firstRender http://localhost:8088/ui2/assets/vendor.js:2658:245
> renderAndCleanup http://localhost:8088/ui2/assets/vendor.js:2661:189
> _firstRender http://localhost:8088/ui2/assets/vendor.js:2658:55
> invoke http://localhost:8088/ui2/assets/vendor.js:2657:203
> yieldKeyword http://localhost:8088/ui2/assets/vendor.js:991:888
> handleKeyword http://localhost:8088/ui2/assets/vendor.js:2512:40
> handleRedirect http://localhost:8088/ui2/assets/vendor.js:2509:4
> inline http://localhost:8088/ui2/assets/vendor.js:2528:62
> content http://localhost:8088/ui2/assets/vendor.js:2572:903
> populateNodes http://localhost:8088/ui2/assets/vendor.js:2610:181
> render http://localhost:8088/ui2/assets/vendor.js:2605:265
> render http://localhost:80
[jira] [Comment Edited] (YARN-9240) YARN UI 2 footer shows the datetime in different timezone
[
https://issues.apache.org/jira/browse/YARN-9240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16756000#comment-16756000
]
Akhil PB edited comment on YARN-9240 at 1/30/19 11:25 AM:
--
Hi [~masatana]
So YARN-8747 patch fixes the this issue, right? Because I could not figure out
the moment-timezone fix version from the PR given above. If the issue is fixed
in the version > 0.5.1, then we may need to update the moment-timezone.
YARN-8747 updates from 0.5.0 to 0.5.1.
was (Author: akhilpb):
Hi [~masatana]
So YARN-8747 patch fixes the issue you mentioned above, right? Because I could
not figure out the moment-timezone fix version from the PR given above.
> YARN UI 2 footer shows the datetime in different timezone
> -
>
> Key: YARN-9240
> URL: https://issues.apache.org/jira/browse/YARN-9240
> Project: Hadoop YARN
> Issue Type: Bug
> Components: yarn-ui-v2
>Affects Versions: 3.2.0
> Environment: Windows 10/Firefox 64
> {code}
> (new Date()).toTimeString()
> => "09:11:16 GMT+0900 (日本標準時)"
> {code}
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Minor
>
> YARN Web UI 2 footer shows the started time about "2019-01-25 16:39" even if
> the ResourceManager started at "2019-01-26 00:39:34"(UTC), and my PC's
> localtime is JST.(+09:00 GMT)
> ResourceManager log is below: (Sever time is set as UTC).
> {code}
> 2019-01-26 00:39:34,619 INFO
> org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: STARTUP_MSG:
> /
> STARTUP_MSG: Starting ResourceManager
> STARTUP_MSG: host = X/X
> STARTUP_MSG: args = []
> STARTUP_MSG: version = 3.2.0
> (snip)
> {code}
> Web browser console outputs an error like below
> {code:java}
> TypeError: "c[0].match(...) is null"
> i http://localhost:8088/ui2/assets/vendor.js:5598:40973
> l http://localhost:8088/ui2/assets/vendor.js:5598:41338
> p http://localhost:8088/ui2/assets/vendor.js:5598:42035
> q http://localhost:8088/ui2/assets/vendor.js:5598:42235
> getDefaultTimezone http://localhost:8088/ui2/assets/yarn-ui.js:378:464
> convertTimestampWithTz
> http://localhost:8088/ui2/assets/yarn-ui.js:379:220
> timeStampToDate http://localhost:8088/ui2/assets/yarn-ui.js:360:80
> dateFormatter http://localhost:8088/ui2/assets/yarn-ui.js:177:1011
> compute http://localhost:8088/ui2/assets/vendor.js:1052:780
> value http://localhost:8088/ui2/assets/vendor.js:1528:12
> read http://localhost:8088/ui2/assets/vendor.js:1544:58
> readArray http://localhost:8088/ui2/assets/vendor.js:1545:110
> compute http://localhost:8088/ui2/assets/vendor.js:1553:317
> value http://localhost:8088/ui2/assets/vendor.js:1528:12
> read http://localhost:8088/ui2/assets/vendor.js:1544:58
> getValue http://localhost:8088/ui2/assets/vendor.js:907:329
> attribute http://localhost:8088/ui2/assets/vendor.js:2547:54
> attribute http://localhost:8088/ui2/assets/vendor.js:2575:623
> populateNodes http://localhost:8088/ui2/assets/vendor.js:2610:334
> render http://localhost:8088/ui2/assets/vendor.js:2605:265
> render http://localhost:8088/ui2/assets/vendor.js:2579:122
> yieldTemplate http://localhost:8088/ui2/assets/vendor.js:2479:155
> ifUnless http://localhost:8088/ui2/assets/vendor.js:871:85
> ifHelper http://localhost:8088/ui2/assets/vendor.js:869:524
> compute http://localhost:8088/ui2/assets/vendor.js:1051:500
> value http://localhost:8088/ui2/assets/vendor.js:1528:12
> invokeHelper http://localhost:8088/ui2/assets/vendor.js:914:14
> continueBlock http://localhost:8088/ui2/assets/vendor.js:2504:214
> renderAndCleanup http://localhost:8088/ui2/assets/vendor.js:2661:189
> hostBlock http://localhost:8088/ui2/assets/vendor.js:2505:150
> continueBlock http://localhost:8088/ui2/assets/vendor.js:2504:83
> block http://localhost:8088/ui2/assets/vendor.js:2503:1
> block http://localhost:8088/ui2/assets/vendor.js:2572:288
> populateNodes http://localhost:8088/ui2/assets/vendor.js:2610:34
> render http://localhost:8088/ui2/assets/vendor.js:2605:265
> render http://localhost:8088/ui2/assets/vendor.js:2579:122
> _firstRender http://localhost:8088/ui2/assets/vendor.js:2658:245
> renderAndCleanup http://localhost:8088/ui2/assets/vendor.js:2661:189
> _firstRender http://localhost:8088/ui2/assets/vendor.js:2658:55
> invoke http://localhost:8088/ui2/assets/vendor.js:2657:203
> yieldKeyword http://localhost:8088/ui2/assets/vendor.js:991:888
> handleKeyword http://localhost:8088/ui2/assets/vendor.js:2512:40
> handleRed
[jira] [Updated] (YARN-7824) [UI2] Yarn Component Instance page should include link to container logs
[ https://issues.apache.org/jira/browse/YARN-7824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-7824: --- Attachment: YARN-7824.001.patch > [UI2] Yarn Component Instance page should include link to container logs > > > Key: YARN-7824 > URL: https://issues.apache.org/jira/browse/YARN-7824 > Project: Hadoop YARN > Issue Type: Improvement > Components: yarn-ui-v2 >Affects Versions: 3.0.0 >Reporter: Yesha Vora >Assignee: Akhil PB >Priority: Major > Attachments: YARN-7824.001.patch > > > Steps: > 1) Launch Httpd example > 2) Visit component Instance page for httpd-proxy-0 > This page has information regarding httpd-proxy-0 component. > This page should also include a link to container logs for this component > h2. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (YARN-7761) [UI2] Clicking 'master container log' or 'Link' next to 'log' under application's appAttempt goes to Old UI's Log link
[ https://issues.apache.org/jira/browse/YARN-7761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16753719#comment-16753719 ] Akhil PB edited comment on YARN-7761 at 1/28/19 7:27 AM: - Attached a patch for branch-3.2. cc [~sunilg] was (Author: akhilpb): Attached a patch for branch-3.2 > [UI2] Clicking 'master container log' or 'Link' next to 'log' under > application's appAttempt goes to Old UI's Log link > -- > > Key: YARN-7761 > URL: https://issues.apache.org/jira/browse/YARN-7761 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Sumana Sathish >Assignee: Akhil PB >Priority: Major > Fix For: 3.3.0 > > Attachments: YARN-7761-branch-3.2.001.patch, YARN-7761.001.patch, > YARN-7761.002.patch, YARN-7761.003.patch > > > Clicking 'master container log' or 'Link' next to 'Log' under application's > appAttempt goes to Old UI's Log link -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7761) [UI2] Clicking 'master container log' or 'Link' next to 'log' under application's appAttempt goes to Old UI's Log link
[ https://issues.apache.org/jira/browse/YARN-7761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16753719#comment-16753719 ] Akhil PB commented on YARN-7761: Attached a patch for branch-3.2 > [UI2] Clicking 'master container log' or 'Link' next to 'log' under > application's appAttempt goes to Old UI's Log link > -- > > Key: YARN-7761 > URL: https://issues.apache.org/jira/browse/YARN-7761 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Sumana Sathish >Assignee: Akhil PB >Priority: Major > Fix For: 3.3.0 > > Attachments: YARN-7761-branch-3.2.001.patch, YARN-7761.001.patch, > YARN-7761.002.patch, YARN-7761.003.patch > > > Clicking 'master container log' or 'Link' next to 'Log' under application's > appAttempt goes to Old UI's Log link -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7761) [UI2] Clicking 'master container log' or 'Link' next to 'log' under application's appAttempt goes to Old UI's Log link
[ https://issues.apache.org/jira/browse/YARN-7761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-7761: --- Attachment: YARN-7761-branch-3.2.001.patch > [UI2] Clicking 'master container log' or 'Link' next to 'log' under > application's appAttempt goes to Old UI's Log link > -- > > Key: YARN-7761 > URL: https://issues.apache.org/jira/browse/YARN-7761 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Sumana Sathish >Assignee: Akhil PB >Priority: Major > Fix For: 3.3.0 > > Attachments: YARN-7761-branch-3.2.001.patch, YARN-7761.001.patch, > YARN-7761.002.patch, YARN-7761.003.patch > > > Clicking 'master container log' or 'Link' next to 'Log' under application's > appAttempt goes to Old UI's Log link -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7761) [UI2] Clicking 'master container log' or 'Link' next to 'log' under application's appAttempt goes to Old UI's Log link
[ https://issues.apache.org/jira/browse/YARN-7761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16751324#comment-16751324 ] Akhil PB commented on YARN-7761: Attached v3 patch, which provides log link, clicking on which redirects to UI2 logs page by pre-populating attemptId and containerId. > [UI2] Clicking 'master container log' or 'Link' next to 'log' under > application's appAttempt goes to Old UI's Log link > -- > > Key: YARN-7761 > URL: https://issues.apache.org/jira/browse/YARN-7761 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Sumana Sathish >Assignee: Akhil PB >Priority: Major > Attachments: YARN-7761.001.patch, YARN-7761.002.patch, > YARN-7761.003.patch > > > Clicking 'master container log' or 'Link' next to 'Log' under application's > appAttempt goes to Old UI's Log link -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7761) [UI2] Clicking 'master container log' or 'Link' next to 'log' under application's appAttempt goes to Old UI's Log link
[ https://issues.apache.org/jira/browse/YARN-7761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-7761: --- Attachment: YARN-7761.003.patch > [UI2] Clicking 'master container log' or 'Link' next to 'log' under > application's appAttempt goes to Old UI's Log link > -- > > Key: YARN-7761 > URL: https://issues.apache.org/jira/browse/YARN-7761 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Sumana Sathish >Assignee: Akhil PB >Priority: Major > Attachments: YARN-7761.001.patch, YARN-7761.002.patch, > YARN-7761.003.patch > > > Clicking 'master container log' or 'Link' next to 'Log' under application's > appAttempt goes to Old UI's Log link -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7761) [UI2] Clicking 'master container log' or 'Link' next to 'log' under application's appAttempt goes to Old UI's Log link
[ https://issues.apache.org/jira/browse/YARN-7761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16750922#comment-16750922 ] Akhil PB commented on YARN-7761: Attached v2 patch, which implements following: # Provides two links for logs # First link (Link1) redirects to UI2 logs page by pre-populating attemptId and containerId. # Second link (Link2) redirects to legacy RM UI (UI1) logs page. [~sunilg] [~rohithsharma] please help to review and commit the patch. > [UI2] Clicking 'master container log' or 'Link' next to 'log' under > application's appAttempt goes to Old UI's Log link > -- > > Key: YARN-7761 > URL: https://issues.apache.org/jira/browse/YARN-7761 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Sumana Sathish >Assignee: Akhil PB >Priority: Major > Attachments: YARN-7761.001.patch, YARN-7761.002.patch > > > Clicking 'master container log' or 'Link' next to 'Log' under application's > appAttempt goes to Old UI's Log link -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7761) [UI2] Clicking 'master container log' or 'Link' next to 'log' under application's appAttempt goes to Old UI's Log link
[ https://issues.apache.org/jira/browse/YARN-7761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-7761: --- Attachment: YARN-7761.002.patch > [UI2] Clicking 'master container log' or 'Link' next to 'log' under > application's appAttempt goes to Old UI's Log link > -- > > Key: YARN-7761 > URL: https://issues.apache.org/jira/browse/YARN-7761 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Sumana Sathish >Assignee: Akhil PB >Priority: Major > Attachments: YARN-7761.001.patch, YARN-7761.002.patch > > > Clicking 'master container log' or 'Link' next to 'Log' under application's > appAttempt goes to Old UI's Log link -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-9215) RM throws NPE and shutdown when trying to stop a service
[
https://issues.apache.org/jira/browse/YARN-9215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749596#comment-16749596
]
Akhil PB commented on YARN-9215:
This is duplicate of YARN-6695. Closing it as duplicate
> RM throws NPE and shutdown when trying to stop a service
>
>
> Key: YARN-9215
> URL: https://issues.apache.org/jira/browse/YARN-9215
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager, yarn-native-services
>Affects Versions: 3.3.0
>Reporter: Akhil PB
>Priority: Critical
>
> When trying to stop the service from UI2, RM shutsdown and throws NPE.
> {code:java}
> 2019-01-21 16:22:13,548 INFO
> org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl: Type-specific
> cleanup of application application_1548064352792_0002 of type yarn-service
> succeeded
> 2019-01-21 16:22:13,549 INFO
> org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl:
> application_1548064352792_0002 State change from FINISHING to FINISHED on
> event = ATTEMPT_FINISHED
> 2019-01-21 16:22:13,549 INFO
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler:
> Application Attempt appattempt_1548064352792_0002_01 is done.
> finalState=FINISHED
> 2019-01-21 16:22:13,549 INFO
> org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger: USER=dr.who
> OPERATION=Application Finished - Succeeded TARGET=RMAppManager
> RESULT=SUCCESS APPID=application_1548064352792_0002
> 2019-01-21 16:22:13,549 INFO
> org.apache.hadoop.yarn.server.resourcemanager.rmcontainer.RMContainerImpl:
> container_1548064352792_0002_01_03 Container Transitioned from RUNNING to
> KILLED
> 2019-01-21 16:22:13,549 INFO
> org.apache.hadoop.yarn.server.resourcemanager.amlauncher.AMLauncher: Cleaning
> master appattempt_1548064352792_0002_01
> 2019-01-21 16:22:13,549 INFO
> org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger: USER=dr.who
> OPERATION=AM Released Container TARGET=SchedulerApp RESULT=SUCCESS
> APPID=application_1548064352792_0002
> CONTAINERID=container_1548064352792_0002_01_03
> RESOURCE=QUEUENAME=default
> 2019-01-21 16:22:13,549 FATAL org.apache.hadoop.yarn.event.AsyncDispatcher:
> Error in dispatcher thread
> java.lang.NullPointerException
> at
> org.apache.hadoop.yarn.server.resourcemanager.metrics.TimelineServiceV2Publisher.putEntity(TimelineServiceV2Publisher.java:462)
> at
> org.apache.hadoop.yarn.server.resourcemanager.metrics.TimelineServiceV2Publisher.access$100(TimelineServiceV2Publisher.java:73)
> at
> org.apache.hadoop.yarn.server.resourcemanager.metrics.TimelineServiceV2Publisher$TimelineV2EventHandler.handle(TimelineServiceV2Publisher.java:497)
> at
> org.apache.hadoop.yarn.server.resourcemanager.metrics.TimelineServiceV2Publisher$TimelineV2EventHandler.handle(TimelineServiceV2Publisher.java:486)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:197)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:126)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> cc [~sunilg] [~rohithsharma]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Resolved] (YARN-9215) RM throws NPE and shutdown when trying to stop a service
[
https://issues.apache.org/jira/browse/YARN-9215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akhil PB resolved YARN-9215.
Resolution: Duplicate
> RM throws NPE and shutdown when trying to stop a service
>
>
> Key: YARN-9215
> URL: https://issues.apache.org/jira/browse/YARN-9215
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager, yarn-native-services
>Affects Versions: 3.3.0
>Reporter: Akhil PB
>Priority: Critical
>
> When trying to stop the service from UI2, RM shutsdown and throws NPE.
> {code:java}
> 2019-01-21 16:22:13,548 INFO
> org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl: Type-specific
> cleanup of application application_1548064352792_0002 of type yarn-service
> succeeded
> 2019-01-21 16:22:13,549 INFO
> org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl:
> application_1548064352792_0002 State change from FINISHING to FINISHED on
> event = ATTEMPT_FINISHED
> 2019-01-21 16:22:13,549 INFO
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler:
> Application Attempt appattempt_1548064352792_0002_01 is done.
> finalState=FINISHED
> 2019-01-21 16:22:13,549 INFO
> org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger: USER=dr.who
> OPERATION=Application Finished - Succeeded TARGET=RMAppManager
> RESULT=SUCCESS APPID=application_1548064352792_0002
> 2019-01-21 16:22:13,549 INFO
> org.apache.hadoop.yarn.server.resourcemanager.rmcontainer.RMContainerImpl:
> container_1548064352792_0002_01_03 Container Transitioned from RUNNING to
> KILLED
> 2019-01-21 16:22:13,549 INFO
> org.apache.hadoop.yarn.server.resourcemanager.amlauncher.AMLauncher: Cleaning
> master appattempt_1548064352792_0002_01
> 2019-01-21 16:22:13,549 INFO
> org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger: USER=dr.who
> OPERATION=AM Released Container TARGET=SchedulerApp RESULT=SUCCESS
> APPID=application_1548064352792_0002
> CONTAINERID=container_1548064352792_0002_01_03
> RESOURCE=QUEUENAME=default
> 2019-01-21 16:22:13,549 FATAL org.apache.hadoop.yarn.event.AsyncDispatcher:
> Error in dispatcher thread
> java.lang.NullPointerException
> at
> org.apache.hadoop.yarn.server.resourcemanager.metrics.TimelineServiceV2Publisher.putEntity(TimelineServiceV2Publisher.java:462)
> at
> org.apache.hadoop.yarn.server.resourcemanager.metrics.TimelineServiceV2Publisher.access$100(TimelineServiceV2Publisher.java:73)
> at
> org.apache.hadoop.yarn.server.resourcemanager.metrics.TimelineServiceV2Publisher$TimelineV2EventHandler.handle(TimelineServiceV2Publisher.java:497)
> at
> org.apache.hadoop.yarn.server.resourcemanager.metrics.TimelineServiceV2Publisher$TimelineV2EventHandler.handle(TimelineServiceV2Publisher.java:486)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:197)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:126)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> cc [~sunilg] [~rohithsharma]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9142) UI cluster nodes page is broken
[ https://issues.apache.org/jira/browse/YARN-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-9142: --- Fix Version/s: 3.1.3 3.2.1 3.3.0 3.1.2 3.0.4 > UI cluster nodes page is broken > --- > > Key: YARN-9142 > URL: https://issues.apache.org/jira/browse/YARN-9142 > Project: Hadoop YARN > Issue Type: Bug >Affects Versions: 3.1.2, 3.3.0 >Reporter: Rohith Sharma K S >Assignee: Akhil PB >Priority: Critical > Fix For: 3.0.4, 3.1.2, 3.3.0, 3.2.1, 3.1.3 > > Attachments: ClusterNodePage.png, > cluster-nodes-page-hadoop-3.3.0-SNAPSHOT.png > > > It is observed in trunk build YARN cluster node pages is broken even though > data exist. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Reopened] (YARN-9142) UI cluster nodes page is broken
[ https://issues.apache.org/jira/browse/YARN-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB reopened YARN-9142: > UI cluster nodes page is broken > --- > > Key: YARN-9142 > URL: https://issues.apache.org/jira/browse/YARN-9142 > Project: Hadoop YARN > Issue Type: Bug >Affects Versions: 3.1.2, 3.3.0 >Reporter: Rohith Sharma K S >Assignee: Akhil PB >Priority: Critical > Fix For: 3.0.4, 3.1.2, 3.3.0, 3.2.1, 3.1.3 > > Attachments: ClusterNodePage.png, > cluster-nodes-page-hadoop-3.3.0-SNAPSHOT.png > > > It is observed in trunk build YARN cluster node pages is broken even though > data exist. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Resolved] (YARN-9142) UI cluster nodes page is broken
[ https://issues.apache.org/jira/browse/YARN-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB resolved YARN-9142. Resolution: Duplicate > UI cluster nodes page is broken > --- > > Key: YARN-9142 > URL: https://issues.apache.org/jira/browse/YARN-9142 > Project: Hadoop YARN > Issue Type: Bug >Affects Versions: 3.1.2, 3.3.0 >Reporter: Rohith Sharma K S >Assignee: Akhil PB >Priority: Critical > Fix For: 3.0.4, 3.1.2, 3.3.0, 3.2.1, 3.1.3 > > Attachments: ClusterNodePage.png, > cluster-nodes-page-hadoop-3.3.0-SNAPSHOT.png > > > It is observed in trunk build YARN cluster node pages is broken even though > data exist. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Resolved] (YARN-9142) UI cluster nodes page is broken
[ https://issues.apache.org/jira/browse/YARN-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB resolved YARN-9142. Resolution: Fixed Resolving the ticket since YARN-9210 is fixed. > UI cluster nodes page is broken > --- > > Key: YARN-9142 > URL: https://issues.apache.org/jira/browse/YARN-9142 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Rohith Sharma K S >Assignee: Akhil PB >Priority: Critical > Attachments: ClusterNodePage.png, > cluster-nodes-page-hadoop-3.3.0-SNAPSHOT.png > > > It is observed in trunk build YARN cluster node pages is broken even though > data exist. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9142) UI cluster nodes page is broken
[ https://issues.apache.org/jira/browse/YARN-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-9142: --- Affects Version/s: 3.3.0 3.1.2 > UI cluster nodes page is broken > --- > > Key: YARN-9142 > URL: https://issues.apache.org/jira/browse/YARN-9142 > Project: Hadoop YARN > Issue Type: Bug >Affects Versions: 3.1.2, 3.3.0 >Reporter: Rohith Sharma K S >Assignee: Akhil PB >Priority: Critical > Attachments: ClusterNodePage.png, > cluster-nodes-page-hadoop-3.3.0-SNAPSHOT.png > > > It is observed in trunk build YARN cluster node pages is broken even though > data exist. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9215) RM throws NPE and shutdown when trying to stop a service
[
https://issues.apache.org/jira/browse/YARN-9215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akhil PB updated YARN-9215:
---
Summary: RM throws NPE and shutdown when trying to stop a service (was: RM
throws NPE when trying to stop a service)
> RM throws NPE and shutdown when trying to stop a service
>
>
> Key: YARN-9215
> URL: https://issues.apache.org/jira/browse/YARN-9215
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager, yarn-native-services
>Affects Versions: 3.3.0
>Reporter: Akhil PB
>Priority: Critical
>
> When trying to stop the service from UI2, RM shutsdown and throws NPE.
> {code:java}
> 2019-01-21 16:22:13,548 INFO
> org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl: Type-specific
> cleanup of application application_1548064352792_0002 of type yarn-service
> succeeded
> 2019-01-21 16:22:13,549 INFO
> org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl:
> application_1548064352792_0002 State change from FINISHING to FINISHED on
> event = ATTEMPT_FINISHED
> 2019-01-21 16:22:13,549 INFO
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler:
> Application Attempt appattempt_1548064352792_0002_01 is done.
> finalState=FINISHED
> 2019-01-21 16:22:13,549 INFO
> org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger: USER=dr.who
> OPERATION=Application Finished - Succeeded TARGET=RMAppManager
> RESULT=SUCCESS APPID=application_1548064352792_0002
> 2019-01-21 16:22:13,549 INFO
> org.apache.hadoop.yarn.server.resourcemanager.rmcontainer.RMContainerImpl:
> container_1548064352792_0002_01_03 Container Transitioned from RUNNING to
> KILLED
> 2019-01-21 16:22:13,549 INFO
> org.apache.hadoop.yarn.server.resourcemanager.amlauncher.AMLauncher: Cleaning
> master appattempt_1548064352792_0002_01
> 2019-01-21 16:22:13,549 INFO
> org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger: USER=dr.who
> OPERATION=AM Released Container TARGET=SchedulerApp RESULT=SUCCESS
> APPID=application_1548064352792_0002
> CONTAINERID=container_1548064352792_0002_01_03
> RESOURCE=QUEUENAME=default
> 2019-01-21 16:22:13,549 FATAL org.apache.hadoop.yarn.event.AsyncDispatcher:
> Error in dispatcher thread
> java.lang.NullPointerException
> at
> org.apache.hadoop.yarn.server.resourcemanager.metrics.TimelineServiceV2Publisher.putEntity(TimelineServiceV2Publisher.java:462)
> at
> org.apache.hadoop.yarn.server.resourcemanager.metrics.TimelineServiceV2Publisher.access$100(TimelineServiceV2Publisher.java:73)
> at
> org.apache.hadoop.yarn.server.resourcemanager.metrics.TimelineServiceV2Publisher$TimelineV2EventHandler.handle(TimelineServiceV2Publisher.java:497)
> at
> org.apache.hadoop.yarn.server.resourcemanager.metrics.TimelineServiceV2Publisher$TimelineV2EventHandler.handle(TimelineServiceV2Publisher.java:486)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:197)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:126)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> cc [~sunilg] [~rohithsharma]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9215) RM throws NPE when trying to stop a service
[
https://issues.apache.org/jira/browse/YARN-9215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akhil PB updated YARN-9215:
---
Component/s: yarn-native-services
> RM throws NPE when trying to stop a service
> ---
>
> Key: YARN-9215
> URL: https://issues.apache.org/jira/browse/YARN-9215
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager, yarn-native-services, yarn-ui-v2
>Affects Versions: 3.3.0
>Reporter: Akhil PB
>Priority: Critical
>
> When trying to stop the service from UI2, RM shutsdown and throws NPE.
> {code:java}
> 2019-01-21 16:22:13,548 INFO
> org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl: Type-specific
> cleanup of application application_1548064352792_0002 of type yarn-service
> succeeded
> 2019-01-21 16:22:13,549 INFO
> org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl:
> application_1548064352792_0002 State change from FINISHING to FINISHED on
> event = ATTEMPT_FINISHED
> 2019-01-21 16:22:13,549 INFO
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler:
> Application Attempt appattempt_1548064352792_0002_01 is done.
> finalState=FINISHED
> 2019-01-21 16:22:13,549 INFO
> org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger: USER=dr.who
> OPERATION=Application Finished - Succeeded TARGET=RMAppManager
> RESULT=SUCCESS APPID=application_1548064352792_0002
> 2019-01-21 16:22:13,549 INFO
> org.apache.hadoop.yarn.server.resourcemanager.rmcontainer.RMContainerImpl:
> container_1548064352792_0002_01_03 Container Transitioned from RUNNING to
> KILLED
> 2019-01-21 16:22:13,549 INFO
> org.apache.hadoop.yarn.server.resourcemanager.amlauncher.AMLauncher: Cleaning
> master appattempt_1548064352792_0002_01
> 2019-01-21 16:22:13,549 INFO
> org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger: USER=dr.who
> OPERATION=AM Released Container TARGET=SchedulerApp RESULT=SUCCESS
> APPID=application_1548064352792_0002
> CONTAINERID=container_1548064352792_0002_01_03
> RESOURCE=QUEUENAME=default
> 2019-01-21 16:22:13,549 FATAL org.apache.hadoop.yarn.event.AsyncDispatcher:
> Error in dispatcher thread
> java.lang.NullPointerException
> at
> org.apache.hadoop.yarn.server.resourcemanager.metrics.TimelineServiceV2Publisher.putEntity(TimelineServiceV2Publisher.java:462)
> at
> org.apache.hadoop.yarn.server.resourcemanager.metrics.TimelineServiceV2Publisher.access$100(TimelineServiceV2Publisher.java:73)
> at
> org.apache.hadoop.yarn.server.resourcemanager.metrics.TimelineServiceV2Publisher$TimelineV2EventHandler.handle(TimelineServiceV2Publisher.java:497)
> at
> org.apache.hadoop.yarn.server.resourcemanager.metrics.TimelineServiceV2Publisher$TimelineV2EventHandler.handle(TimelineServiceV2Publisher.java:486)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:197)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:126)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> cc [~sunilg] [~rohithsharma]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9215) RM throws NPE when trying to stop a service
[
https://issues.apache.org/jira/browse/YARN-9215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akhil PB updated YARN-9215:
---
Component/s: (was: yarn-ui-v2)
> RM throws NPE when trying to stop a service
> ---
>
> Key: YARN-9215
> URL: https://issues.apache.org/jira/browse/YARN-9215
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager, yarn-native-services
>Affects Versions: 3.3.0
>Reporter: Akhil PB
>Priority: Critical
>
> When trying to stop the service from UI2, RM shutsdown and throws NPE.
> {code:java}
> 2019-01-21 16:22:13,548 INFO
> org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl: Type-specific
> cleanup of application application_1548064352792_0002 of type yarn-service
> succeeded
> 2019-01-21 16:22:13,549 INFO
> org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl:
> application_1548064352792_0002 State change from FINISHING to FINISHED on
> event = ATTEMPT_FINISHED
> 2019-01-21 16:22:13,549 INFO
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler:
> Application Attempt appattempt_1548064352792_0002_01 is done.
> finalState=FINISHED
> 2019-01-21 16:22:13,549 INFO
> org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger: USER=dr.who
> OPERATION=Application Finished - Succeeded TARGET=RMAppManager
> RESULT=SUCCESS APPID=application_1548064352792_0002
> 2019-01-21 16:22:13,549 INFO
> org.apache.hadoop.yarn.server.resourcemanager.rmcontainer.RMContainerImpl:
> container_1548064352792_0002_01_03 Container Transitioned from RUNNING to
> KILLED
> 2019-01-21 16:22:13,549 INFO
> org.apache.hadoop.yarn.server.resourcemanager.amlauncher.AMLauncher: Cleaning
> master appattempt_1548064352792_0002_01
> 2019-01-21 16:22:13,549 INFO
> org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger: USER=dr.who
> OPERATION=AM Released Container TARGET=SchedulerApp RESULT=SUCCESS
> APPID=application_1548064352792_0002
> CONTAINERID=container_1548064352792_0002_01_03
> RESOURCE=QUEUENAME=default
> 2019-01-21 16:22:13,549 FATAL org.apache.hadoop.yarn.event.AsyncDispatcher:
> Error in dispatcher thread
> java.lang.NullPointerException
> at
> org.apache.hadoop.yarn.server.resourcemanager.metrics.TimelineServiceV2Publisher.putEntity(TimelineServiceV2Publisher.java:462)
> at
> org.apache.hadoop.yarn.server.resourcemanager.metrics.TimelineServiceV2Publisher.access$100(TimelineServiceV2Publisher.java:73)
> at
> org.apache.hadoop.yarn.server.resourcemanager.metrics.TimelineServiceV2Publisher$TimelineV2EventHandler.handle(TimelineServiceV2Publisher.java:497)
> at
> org.apache.hadoop.yarn.server.resourcemanager.metrics.TimelineServiceV2Publisher$TimelineV2EventHandler.handle(TimelineServiceV2Publisher.java:486)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:197)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:126)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> cc [~sunilg] [~rohithsharma]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
