You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Prateek Maheshwari (JIRA)" <ji...@apache.org> on 2017/04/17 03:17:41 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 ]

Prateek Maheshwari reassigned SAMZA-860:
----------------------------------------

    Assignee: Prateek Maheshwari

> 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: Prateek Maheshwari
>             Fix For: 0.13.0
>
>
> 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.15#6346)