[
https://issues.apache.org/jira/browse/FLINK-15449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17027399#comment-17027399
]
Chesnay Schepler commented on FLINK-15449:
------------------------------------------
I don't see this being feasible. We'd have to retain information on lost
TaskExecutors in the runtime (i.e., the REST API layer would not be
sufficient), and we don't want any additional complexity in there.
> 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)
