[
https://issues.apache.org/jira/browse/FLINK-32469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hong Liang Teoh updated FLINK-32469:
------------------------------------
Description:
*Why*
We want to enable programmatic use of the checkpoints REST API, independent of
the Flink dashboard.
Currently, REST APIs that retrieve information relating to a given Flink job
passes through the
The current configuration of the `ExecutionGraph` cache is meant to facilitate
a fluid user experience of the Flink dashboard. On the Job details page, the
Flink dashboard makes a series of requests (e.g. /jobs/\{jobid},
/jobs/\{jobid}/vertices/\{vertexid}){color:#172b4d}. {color}
{color:#172b4d}To ensure that the requests return consistent results, we have
the execution graph cache.{color}
*What*
The checkpoint handlers currently retrieve checkpoint information from the
`ExecutionGraph`, which is cached in the `AbstractExecutionGraphHandler`. This
means that this information is potentially stale (depending on the
`web.refresh-interval`, which defaults to 3s).
We want to make the checkpoint handlers directly retrieve the latest
`CheckpointStatsSnapshot` object instead of relying on the cached
`ExecutionGraph`.
was:
*What*
The checkpoint handlers currently retrieve checkpoint information from the
`ExecutionGraph`, which is cached in the `AbstractExecutionGraphHandler`. This
means that this information is potentially stale (depending on the
`web.refresh-interval`, which defaults to 3s).
We want to make the checkpoint handlers directly retrieve the latest
`CheckpointStatsSnapshot` object instead of relying on the cached
`ExecutionGraph`.
*Why*
We want to enable programmatic use of the REST API, independent of the Flink
dashboard.
The current configuration of the `ExecutionGraph` cache is meant to facilitate
a fluid user experience of the Flink dashboard. On the Job details page, the
Flink dashboard makes a series of requests (e.g. /jobs/\{jobid},
/jobs/\{jobid}/vertices/\{vertexid}){color:#172b4d}. {color}
{color:#172b4d}To ensure that the requests return consistent results, we have
the execution graph cache.{color}
> Improve checkpoint REST APIs for programmatic access
> ----------------------------------------------------
>
> Key: FLINK-32469
> URL: https://issues.apache.org/jira/browse/FLINK-32469
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / REST
> Affects Versions: 1.16.2, 1.17.1
> Reporter: Hong Liang Teoh
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.18.0
>
>
> *Why*
> We want to enable programmatic use of the checkpoints REST API, independent
> of the Flink dashboard.
> Currently, REST APIs that retrieve information relating to a given Flink job
> passes through the
> The current configuration of the `ExecutionGraph` cache is meant to
> facilitate a fluid user experience of the Flink dashboard. On the Job details
> page, the Flink dashboard makes a series of requests (e.g. /jobs/\{jobid},
> /jobs/\{jobid}/vertices/\{vertexid}){color:#172b4d}. {color}
> {color:#172b4d}To ensure that the requests return consistent results, we have
> the execution graph cache.{color}
>
> *What*
> The checkpoint handlers currently retrieve checkpoint information from the
> `ExecutionGraph`, which is cached in the `AbstractExecutionGraphHandler`.
> This means that this information is potentially stale (depending on the
> `web.refresh-interval`, which defaults to 3s).
> We want to make the checkpoint handlers directly retrieve the latest
> `CheckpointStatsSnapshot` object instead of relying on the cached
> `ExecutionGraph`.
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
