You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Hong Liang Teoh (Jira)" <ji...@apache.org> on 2023/06/29 15:28:00 UTC

[jira] [Created] (FLINK-32488) Introduce configuration to control ExecutionGraph cache in REST API

Hong Liang Teoh created FLINK-32488:
---------------------------------------

             Summary: Introduce configuration to control ExecutionGraph cache in REST API
                 Key: FLINK-32488
                 URL: https://issues.apache.org/jira/browse/FLINK-32488
             Project: Flink
          Issue Type: Improvement
          Components: Runtime / REST
    Affects Versions: 1.17.1, 1.16.2
            Reporter: Hong Liang Teoh
             Fix For: 1.18.0


*What*

Currently, REST handlers that inherit from AbstractExecutionGraphHandler serve information derived from a cached ExecutionGraph.

This ExecutionGraph cache currently derives it's timeout from {*}web.refresh-interval{*}. The *web.refresh-interval* controls both the refresh rate of the Flink dashboard and the ExecutionGraph cache timeout. 

We should introduce a new configuration to control the ExecutionGraph cache, namely {*}rest.cache.execution-graph.expiry{*}.

*Why*

Sharing configuration between REST handler and Flink dashboard is a sign that we are coupling the two. 

Ideally, we want our REST API behaviour to independent of the Flink dashboard (e.g. supports programmatic access).

 

 

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)