Re: [PROPOSAL] Improving Flink’s timer management for large state
I also +1 for this very good proposal!
In general, the design is good, especially the part the related to the timer on Heap, but refer to the part of the timer on RocksDB, I think there may still exist some improvement that we can do, I just left the comments on the doc.
On 05/27/2018 15:31，Bowen Li<bowenli86@xxxxxxxxx> wrote：
+1 LGTM. RocksDB timer service is one of the most highly anticipated
features from Flink users, and it's finally coming, officially. I also
would love to see bringing timer more closely to state backend, for the
sake of easier development and maintenance of code.
On Fri, May 25, 2018 at 7:13 AM, Stefan Richter <s.richter@xxxxxxxxxxxxxxxxx
I am currently planning how to improve Flink’s timer management for large
state. In particular, I would like to introduce timer state that is managed
in RocksDB and also to improve the capabilities of the heap-based timer
service, e.g. support for asynchronous checkpoints. You can find a short
outline of my planned approach in this document:
As always, your questions, feedback, and comments are highly appreciated.