[
https://issues.apache.org/jira/browse/YARN-9451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16871431#comment-16871431
]
Weiwei Yang commented on YARN-9451:
-----------------------------------
Thanks. Patch LGTM, I guess that to use the HTTP port is better for people to
find out which NM this is. However, only one thing about the log, this is quite
confusing...
{noformat}
try the nodemanager at yarn-ats-3:45454
{noformat}
shouldn't it be something like,
{noformat}
try to find the container logs in the local directory of nodemanager
yarn-ats-3:45454
{noformat}
can we fix that too?
Thanks
> AggregatedLogsBlock shows wrong NM http port
> --------------------------------------------
>
> Key: YARN-9451
> URL: https://issues.apache.org/jira/browse/YARN-9451
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 3.2.0
> Reporter: Prabhu Joseph
> Assignee: Prabhu Joseph
> Priority: Minor
> Attachments: Screen Shot 2019-06-20 at 7.49.46 PM.png,
> YARN-9451-001.patch, YARN-9451-002.patch
>
>
> AggregatedLogsBlock shows wrong NM http port when aggregated file is not
> available. It shows [http://yarn-ats-3:45454|http://yarn-ats-3:45454/] - NM
> rpc port instead of http port.
> {code:java}
> Logs not available for job_1554476304275_0003. Aggregation may not be
> complete, Check back later or try the nodemanager at yarn-ats-3:45454
> Or see application log at
> http://yarn-ats-3:45454/node/application/application_1554476304275_0003
> {code}
--
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
