You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Bruno Cadonna (Jira)" <ji...@apache.org> on 2021/05/10 08:54:00 UTC

[jira] [Commented] (KAFKA-12766) Consider Disabling WAL-related Options in RocksDB

    [ https://issues.apache.org/jira/browse/KAFKA-12766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17341782#comment-17341782 ] 

Bruno Cadonna commented on KAFKA-12766:
---------------------------------------

I think throwing an exception is too harsh. Additionally, I do not understand how we should disable the option since we do not have control over the `Options` object. I think, if we want to do something about it, ignoring is the best solution. But I am also fine with not doing anything, because Streams disables the WAL anyways. 

> Consider Disabling WAL-related Options in RocksDB
> -------------------------------------------------
>
>                 Key: KAFKA-12766
>                 URL: https://issues.apache.org/jira/browse/KAFKA-12766
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>            Reporter: Bruno Cadonna
>            Priority: Minor
>
> Streams disables the write-ahead log (WAL) provided by RocksDB since it replicates the data in changelog topics. Hence, it does not make much sense to set WAL-related configs for RocksDB instances within Streams.
> Streams could:
> - disable WAL-related options
> - ignore WAL-related options
> - throw an exception when a WAL-related option is set.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)