[
https://issues.apache.org/jira/browse/FLINK-1579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924281#comment-15924281
]
ASF GitHub Bot commented on FLINK-1579:
---------------------------------------
Github user uce commented on a diff in the pull request:
https://github.com/apache/flink/pull/3460#discussion_r105878628
--- Diff:
flink-runtime/src/main/scala/org/apache/flink/runtime/minicluster/LocalFlinkMiniCluster.scala
---
@@ -247,8 +248,11 @@ class LocalFlinkMiniCluster(
// Props for the distributed components
//------------------------------------------------------------------------------------------------
- def getArchiveProps(archiveClass: Class[_ <: MemoryArchivist],
archiveCount: Int): Props = {
- JobManager.getArchiveProps(archiveClass, archiveCount)
+ def getArchiveProps(
+ archiveClass: Class[_ <: MemoryArchivist],
--- End diff --
I think the arguments should have one more level of indentation
> Create a Flink History Server
> -----------------------------
>
> Key: FLINK-1579
> URL: https://issues.apache.org/jira/browse/FLINK-1579
> Project: Flink
> Issue Type: New Feature
> Components: Distributed Coordination
> Affects Versions: 0.9
> Reporter: Robert Metzger
> Assignee: Chesnay Schepler
>
> Right now its not possible to analyze the job results for jobs that ran on
> YARN, because we'll loose the information once the JobManager has stopped.
> Therefore, I propose to implement a "Flink History Server" which serves the
> results from these jobs.
> I haven't started thinking about the implementation, but I suspect it
> involves some JSON files stored in HDFS :)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
