[
https://issues.apache.org/jira/browse/SAMZA-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14299431#comment-14299431
]
Roger Hoover commented on SAMZA-543:
------------------------------------
[~criccomini] That's great. Thanks for trying it out. Can we also safely set
disableDataSync=true for the same reason? Data is being persisted to a
replicated changelog.
bq. you can disable syncing of data files by setting Options::disableDataSync
to true. This can be useful when doing bulk-loading or big idempotent
operations. Once the operation is finished, you can manually call sync() to
flush all dirty buffers to stable storage.
> 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
> Fix For: 0.9.0
>
>
> 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)
