[
https://issues.apache.org/jira/browse/FLINK-1579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924276#comment-15924276
]
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_r105906846
--- Diff:
flink-runtime/src/main/java/org/apache/flink/runtime/jobmanager/JobManagerOptions.java
---
@@ -32,6 +32,13 @@
public static final ConfigOption<Integer> MAX_ATTEMPTS_HISTORY_SIZE =
key("job-manager.max-attempts-history-size").defaultValue(16);
+ /**
+ * The location where the {@link JobManager} stores the archives for
finished jobs.
+ */
+ public static final ConfigOption<String> ARCHIVE_DIR =
+ key("jobmanager.archive.dir")
--- End diff --
Should we rename this to be in line with my other proposal to allow future
changes? E.g. `jobmanager.archive.fs.dir`?
> 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)
