[GitHub] kafka pull request: KAFKA-1489: Global threshold on data retention...

[bendrees <gi...@git.apache.org>]

GitHub user bendrees opened a pull request:

    https://github.com/apache/kafka/pull/1348

    KAFKA-1489: Global threshold on data retention size

    Implemented a "log retention policy" based on keeping a certain
    percentage of disk space free. In dynamic situations where topics
    are added in unpredictable ways, the other log retention
    parameters are not entirely sufficient to prevent out-of-disk
    conditions from occurring. The new log.retention.disk.usage.percent
    parameter provides this guarantee. It is applied after all the
    other retention parameters are applied, at the end of each log
    cleanup cycle. Oldest segments (across all topics) are pruned
    until usage falls below this percentage of each disk's capacity.
    The default value is 100, which effectively disables the feature.
    
    This is my original work and I license the work to the project under
    the project's open source license.
    
    @junrao, @jkreps, @gwenshap

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/bendrees/kafka KAFKA-1489

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/1348.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1348
    
----
commit 26ef1c5e4a432421f9c1dbdac84d19de1d0ccf54
Author: Ben Drees <be...@zenti.com>
Date:   2016-05-09T06:29:48Z

    Implemented a "log retention policy" based on keeping a certain
    percentage of disk space free. In dynamic situations where topics
    are added in unpredictable ways, the other log retention
    parameters are not entirely sufficient to prevent out-of-disk
    conditions from occurring. The new log.retention.disk.usage.percent
    parameter provides this guarantee. It is applied after all the
    other retention parameters are applied, at the end of each log
    cleanup cycle. Oldest segments (across all topics) are pruned
    until usage falls below this percentage of each disk's capacity.
    The default value is 100, which effectively disables the feature.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---