You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Tao Feng (JIRA)" <ji...@apache.org> on 2016/01/19 21:39:39 UTC
[jira] [Assigned] (SAMZA-860) Expose RocksDB log options via Samza
configuration
[ https://issues.apache.org/jira/browse/SAMZA-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tao Feng reassigned SAMZA-860:
------------------------------
Assignee: Tao Feng
> Expose RocksDB log options via Samza configuration
> --------------------------------------------------
>
> Key: SAMZA-860
> URL: https://issues.apache.org/jira/browse/SAMZA-860
> Project: Samza
> Issue Type: Bug
> Reporter: Yi Pan (Data Infrastructure)
> Assignee: Tao Feng
>
> There are requests to expose RocksDB options via Samza configuration. Pasting the email request below:
> {noformat}
> I noticed that the LOG files in each RocksDB kv store grow indefinitely. I
> could set them up via logrotate but it would be cumbersome and against the
> grain. Tried to figure out if RocksDB has a configuration file and I don't
> have a definite answer yet (the one mention is for version 4.3).
> RocksDB does expose methods for this very purpose:
> setMaxLogFileSize
> setMaxManifestFileSize
> setKeepLogFileNum
> Samza should use these to provide a sensible default out-of-the-box.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)