[FLINK-39264][docs] Add docs for application management#27818
Open
eemario wants to merge 1 commit intoapache:masterfrom
Open
[FLINK-39264][docs] Add docs for application management#27818eemario wants to merge 1 commit intoapache:masterfrom
eemario wants to merge 1 commit intoapache:masterfrom
Conversation
Collaborator
eemario
changed the title
davidradl
reviewed
Mar 25, 2026
| Even after all applications are finished, the cluster (and the JobManager) will | ||
| keep running until the session is manually stopped. The lifetime of a Flink | ||
| Session Cluster is therefore not bound to the lifetime of any Flink Job. | ||
| Session Cluster is therefore not bound to the lifetime of any Flink Application. |
Contributor
There was a problem hiding this comment.
of any Flink Application. -> of any Flink Application or job.
davidradl
reviewed
Mar 25, 2026
| * **Cluster Lifecycle**: in a Flink Session Cluster, the client connects to a | ||
| pre-existing, long-running cluster that can accept multiple job submissions. | ||
| Even after all jobs are finished, the cluster (and the JobManager) will | ||
| pre-existing, long-running cluster that can accept multiple application submissions. |
Contributor
There was a problem hiding this comment.
I suggest a hyper link to the definition of application would be useful, or a quick summary.
I wonder if it is still mentioning jobs as well as applications. Or is every job now in an applicaiton?
davidradl
reviewed
Mar 25, 2026
|
|
||
| #### ApplicationResultStore | ||
|
|
||
| The ApplicationResultStore is a Flink component that persists the results of terminated |
Contributor
There was a problem hiding this comment.
It would be worth doing into more detail as to what we mean by Results is this the last checkpoint / savepoint?
davidradl
reviewed
Mar 25, 2026
| **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`. |
Contributor
There was a problem hiding this comment.
is this different from the application results store - as these are archives - it would be worth contrasting the two if they are different or referring to them in the same way if they are the same.
davidradl
reviewed
Mar 25, 2026
|
|
||
| - `/applications/overview` | ||
| - `/applications/<applicationid>` | ||
| - `/applications/<applicationid>/jobmanager/config` |
Contributor
There was a problem hiding this comment.
can you see the jobs that were under an application? This would seem to be the most useful thing you would want to see.
davidradl
reviewed
Mar 25, 2026
|
|
||
| JobManager High Availability (HA) hardens a Flink cluster against JobManager failures. | ||
| This feature ensures that a Flink cluster will always continue executing your submitted jobs. | ||
| This feature ensures that a Flink cluster will always re-execute your submitted applications that were running at the time of a failure. |
davidradl
reviewed
Mar 25, 2026
| The HA data will be kept until the respective job either succeeds, is cancelled or fails terminally. | ||
| Once this happens, all the HA data, including the metadata stored in the HA services, will be deleted. | ||
| In order to recover submitted applications, Flink persists metadata for the applications. | ||
| The HA data will be kept until the respective application either succeeds, is cancelled or fails terminally. |
Contributor
There was a problem hiding this comment.
I am curious what fails terminally might mean - some examples of types of this would be useful.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is the purpose of the change
This pull request adds docs for application management.
Brief change log
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:
@Public(Evolving): (no)Documentation