You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Navina Ramesh (JIRA)" <ji...@apache.org> on 2015/03/12 23:29:38 UTC

[jira] [Updated] (SAMZA-543) Disable WAL in RocksDB KV store

     [ https://issues.apache.org/jira/browse/SAMZA-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Navina Ramesh updated SAMZA-543:
--------------------------------
    Attachment: SAMZA-543-0.patch

I made changes to disable WAL. Verified it with the hello-samza jobs. Log file is empty. bin/check-all was successful. 

> Disable WAL in RocksDB KV store
> -------------------------------
>
>                 Key: SAMZA-543
>                 URL: https://issues.apache.org/jira/browse/SAMZA-543
>             Project: Samza
>          Issue Type: Bug
>          Components: kv
>    Affects Versions: 0.9.0
>            Reporter: Chris Riccomini
>            Assignee: Navina Ramesh
>             Fix For: 0.9.0
>
>         Attachments: SAMZA-543-0.patch
>
>
> RocksDB uses a write-ahead log by default. This is unnecessary in Samza, since we have full durability from a state store's changelog topic. We should [disable the WAL|https://github.com/facebook/rocksdb/wiki/Basic-Operations#asynchronous-writes] in the RocksDB KV store.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)