[
https://issues.apache.org/jira/browse/FLINK-12662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16855643#comment-16855643
]
Till Rohrmann commented on FLINK-12662:
---------------------------------------
Ok, I see the problem. Instead of archiving intermediate states of the job to
the {{HistoryServer}} we could also think about keeping a history of
failures/restart attempts attached to a job. That way one could also see it
from the web UI. Moreover, we would not have the problem that all of the sudden
there are multiple instances of the same job archived. Then we would also not
have to think about how to address the different parts or how to even find them.
> show jobs failover in history server as well
> --------------------------------------------
>
> Key: FLINK-12662
> URL: https://issues.apache.org/jira/browse/FLINK-12662
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / REST
> Reporter: Su Ralph
> Priority: Major
>
> Currently
> [https://ci.apache.org/projects/flink/flink-docs-release-1.8/monitoring/historyserver.html]
> only show the completed jobs (completd, cancel, failed). Not showing any
> intermediate failover.
> Which make the cluster administrator/developer hard to find first place if
> there is two failover happens. Feature ask is to
> - make a failover as a record in history server as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
