[
https://issues.apache.org/jira/browse/FLINK-15449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17028639#comment-17028639
]
Victor Wong commented on FLINK-15449:
-------------------------------------
[~chesnay], as suggested by [~fly_in_gis], we could _use the schema
"http://\{RM_Address:PORT}/node/containerlogs/\{container_id}/\{user}"; to
construct the log url,_ so I think it's feasible to retain a log URL to lost
TMs.
I agree that it would add additional complexity, but it's inconvenient to debug
lost TMs right now, I think it's worth a shot to solve this.
> Retain lost task managers on Flink UI
> -------------------------------------
>
> Key: FLINK-15449
> URL: https://issues.apache.org/jira/browse/FLINK-15449
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / YARN
> Affects Versions: 1.9.1
> Reporter: Victor Wong
> Priority: Major
>
> With Flink on Yarn, sometimes our TaskManager was killed because of OOM or
> heartbeat timeout or whatever reasons, it's not convenient to check out the
> logs of the lost TaskManger.
> Can we retain the lost task managers on Flink UI, and provide the log service
> through Yarn (we can redirect the URL of log/stdout to Yarn container
> log/stdout)?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
