[
https://issues.apache.org/jira/browse/YARN-9832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Siegl updated YARN-9832:
-------------------------------
Description:
Container logs from yarn UI don't work if the container was on a node that got
deleted as part of a scale down operation. The Appattempts and Containers
points to the NodeManager link of a decommissioned node.
The UI code can change the link to point to Log Server (JHS) if the NM is not
in the Yarn Node List (Running Nodes) or an error page "Node is decommissioned,
check Logs Cli".
was:
Container logs from yarn UI don't work if the container was on a node that got
deleted as part of a scale down operation. The Appattempts and Containers
points to the NodeManager link of a decommissioned node.
The UI code can change the link to point to Log Server (AHS) if the NM is not
in the Yarn Node List (Running Nodes) or an error page "Node is decommissioned,
check Logs Cli".
> YARN UI has decommissioned nodemanager links
> --------------------------------------------
>
> Key: YARN-9832
> URL: https://issues.apache.org/jira/browse/YARN-9832
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 3.3.0
> Reporter: Prabhu Joseph
> Assignee: Tarun Parimi
> Priority: Major
>
> Container logs from yarn UI don't work if the container was on a node that
> got deleted as part of a scale down operation. The Appattempts and Containers
> points to the NodeManager link of a decommissioned node.
> The UI code can change the link to point to Log Server (JHS) if the NM is not
> in the Yarn Node List (Running Nodes) or an error page "Node is
> decommissioned, check Logs Cli".
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
