You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Yi Pan (Data Infrastructure) (JIRA)" <ji...@apache.org> on 2016/01/19 20:58:39 UTC
[jira] [Created] (SAMZA-860) Expose RocksDB log options via Samza
configuration
Yi Pan (Data Infrastructure) created SAMZA-860:
--------------------------------------------------
Summary: 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)
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)