[
https://issues.apache.org/jira/browse/YARN-6314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923333#comment-15923333
]
Junping Du commented on YARN-6314:
----------------------------------
bq. So if NM address is provided by user in the beginning, it sounds like we
will still redirect the request to NM back and forth?
Check offline with Xuan. This is not an issue because the NM return will always
drop NM address. So we are good for this issue.
Latest patch LGTM. +1 pending on Jenkins report.
> Potential infinite redirection on YARN log redirection web service
> ------------------------------------------------------------------
>
> Key: YARN-6314
> URL: https://issues.apache.org/jira/browse/YARN-6314
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Xuan Gong
> Assignee: Xuan Gong
> Attachments: YARN-6314.1.patch, YARN-6314.2.patch
>
>
> In YARN-6113, we have added a re-direct NM web service to get container logs
> which could cause the potential infinite redirection.
> It can happens when:
> * Call AHS web service to get a running/finished AM container log for a
> running application.
> * AHS web service would re-direct the request the specific NM given the
> application is still running. And the NM would handle the request
> * If the log file we requested has already been aggregated and deleted from
> NM, the NM would re-direct the request back to AHS.
> In this case, we would do step 2 and step 3 infinite times.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
