[
https://issues.apache.org/jira/browse/FLINK-18312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chesnay Schepler updated FLINK-18312:
-------------------------------------
Description:
The information about in-progress async operations is currently stored in the
respective REST handler. This means that users cannot query standby Dispatchers
for the status of a savepoint operation.
We should move this state into the Dispatcher.
was:
Savepoint:
1. Deploy our flink cluster in standlone mode on kubernetes and use two
Jobmanagers for HA.
2. Deploy a kubernetes service for the two jobmanagers to provide a unified url.
3. Send a savepoint trigger request to the leader Jobmanager.
4. Query the savepoint status from leader Jobmanager, get correct response.
5. Query the savepoint status from standby Jobmanager, the response will be 404.
Jobmanager log:
1. Query log from leader Jobmanager, get leader log.
2. Query log from standby Jobmanager, get standby log.
Both these two requests will be redirect to the leader in 1.7.
> Move async operation cache into Dispatcher
> -------------------------------------------
>
> Key: FLINK-18312
> URL: https://issues.apache.org/jira/browse/FLINK-18312
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / REST
> Affects Versions: 1.8.0, 1.9.0, 1.10.0
> Reporter: Yu Wang
> Priority: Minor
> Labels: auto-deprioritized-major
>
> The information about in-progress async operations is currently stored in the
> respective REST handler. This means that users cannot query standby
> Dispatchers for the status of a savepoint operation.
> We should move this state into the Dispatcher.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
