[
https://issues.apache.org/jira/browse/FLINK-12662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16850634#comment-16850634
]
vinoyang commented on FLINK-12662:
----------------------------------
[~till.rohrmann] I think your understanding is correct. Considering the [job
status|[https://ci.apache.org/projects/flink/flink-docs-release-1.8/internals/job_scheduling.html]]
state machine, if we could archive the restarting job to the history server,
it would make sense. Otherwise, the intermediate state would be ignored and can
just be found in the log. WDYT? cc [~ralphsu]
> Flink how jobs for 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)
