You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (Jira)" <ji...@apache.org> on 2020/01/17 13:23:01 UTC
[jira] [Commented] (FLINK-10372) There is no API to configure the
timer state backend
[ https://issues.apache.org/jira/browse/FLINK-10372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17018018#comment-17018018 ]
Stephan Ewen commented on FLINK-10372:
--------------------------------------
Is this a duplicate of FLINK-11193 and Flink-10372 ?
> There is no API to configure the timer state backend
> ----------------------------------------------------
>
> Key: FLINK-10372
> URL: https://issues.apache.org/jira/browse/FLINK-10372
> Project: Flink
> Issue Type: Improvement
> Components: API / DataStream, Runtime / State Backends
> Affects Versions: 1.6.0
> Reporter: Elias Levy
> Priority: Minor
>
> Flink 1.6.0, via FLINK-9485, introduced the option to store timers in RocksDB instead of the heap. Alas, this can only be configured via the {{state.backend.rocksdb.timer-service.factory}} config file option. That means that the choice of state backend to use for timer can't be made on a per job basis on a shared cluster.
> There is a need for an API in {{RocksDBStateBackend}} to configure the backend per job.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)