[
https://issues.apache.org/jira/browse/KAFKA-9450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17033915#comment-17033915
]
Sophie Blee-Goldman commented on KAFKA-9450:
--------------------------------------------
[~NaviBrar] I assume that was only merged into the most recent RocksdB version?
We aren't able to bump the rocksdb dependency further until the next major
version bump due to some breaking changes in the options-related API. Not sure
if the rocks folks might be willing to cherry-pick this back to a 5.x version
and release that, if not maybe you should make a ticket to track this and mark
as blocked by KAFKA-8897 so it doesn't get forgotten
> Decouple inner state flushing from committing with EOS
> ------------------------------------------------------
>
> Key: KAFKA-9450
> URL: https://issues.apache.org/jira/browse/KAFKA-9450
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Sophie Blee-Goldman
> Priority: Major
>
> When EOS is turned on, the commit interval is set quite low (100ms) and all
> the store layers are flushed during a commit. This is necessary for
> forwarding records in the cache to the changelog, but unfortunately also
> forces rocksdb to flush the current memtable before it's full. The result is
> a large number of small writes to disk, losing the benefits of batching, and
> a large number of very small L0 files that are likely to slow compaction.
> Since we have to delete the stores to recreate from scratch anyways during an
> unclean shutdown with EOS, we may as well skip flushing the innermost
> StateStore during a commit and only do so during a graceful shutdown, before
> a rebalance, etc. This is currently blocked on a refactoring of the state
> store layers to allow decoupling the flush of the caching layer from the
> actual state store.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
