eemario commented on code in PR #27818:
URL: https://github.com/apache/flink/pull/27818#discussion_r3048938292
##########
docs/content/docs/deployment/advanced/historyserver.md:
##########
@@ -52,20 +52,24 @@ The configuration keys `jobmanager.archive.fs.dir` and
`historyserver.archive.fs
**JobManager**
-The archiving of completed jobs happens on the JobManager, which uploads the
archived job information to a file system directory. You can configure the
directory to archive completed jobs in [Flink configuration file]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) by setting a directory
via `jobmanager.archive.fs.dir`.
+The archiving of completed jobs and applications happens on the JobManager,
which uploads the archived job and application information to a file system
directory. You can configure the directory to archive completed jobs and
applications in [Flink configuration file]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) by setting a directory
via `jobmanager.archive.fs.dir`.
Review Comment:
The History Server and the Application Result Store are indeed completely
different. Here’s the distinction:
- The Application Result Store is an internal mechanism. It stores only
minimal information (e.g., application ID and final status) to mark an
application as "terminated," preventing it from being incorrectly re-submitted
or restarted during a failover.
- The History Server is a user-facing archival tool. It saves detailed
information from completed applications/jobs by caching their REST API
responses (like /applications/:appid, etc.). This allows users to query and
inspect application/job details long after the cluster has shut down.
I have added a brief comparison of the two to the glossary section. Thanks
for the feedback!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
