qinjunjerry commented on a change in pull request #402: URL: https://github.com/apache/flink-web/pull/402#discussion_r555885319
########## File path: _posts/2020-12-20-rocksdb.md ########## @@ -0,0 +1,121 @@ +--- +layout: post +title: "Using RocksDB State Backend in Apache Flink: When and How" +date: 2020-12-20 00:00:00 +authors: +- Jun Qin: + name: "Jun Qin" +excerpt: This blog post will guide you through the benefits of using RocksDB to manage your application’s state, explain when and how to use it and also clear up a few common misconceptions. +--- + +[Stream processing](https://en.wikipedia.org/wiki/Stream_processing) applications are often stateful, “remembering” information from processed events and using it to influence further event processing. In Flink, the remembered information, i.e., state, is stored locally in the configured state backend. To prevent data loss in case of failures, the state backend periodically persists a snapshot of its contents to a pre-configured durable storage. The [RocksDB](https://rocksdb.org/) state backend (i.e., RocksDBStateBackend) is one of the three built-in state backends in Flink. This blog post will guide you through the benefits of using RocksDB to manage your application’s state, explain when and how to use it and also clear up a few common misconceptions. Having said that, this is **not** a blog post to explain how RocksDB works in-depth or how to do advanced troubleshooting and performance tuning; if you need help with any of those topics, you can reach out to the [Flink User M ailing List](https://flink.apache.org/community.html#mailing-lists). Review comment: wikipedia link removed. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
