[
https://issues.apache.org/jira/browse/SAMZA-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16387095#comment-16387095
]
ASF GitHub Bot commented on SAMZA-1600:
---------------------------------------
GitHub user nickpan47 opened a pull request:
https://github.com/apache/samza/pull/435
SAMZA-1600: remove the combination of cleanup policy "compact,delete"…
… in changelog topic properties
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nickpan47/samza SAMZA-1600
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/samza/pull/435.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 #435
----
commit 6549c4f3fe8cb3ca54f60a6f6f966a3c24343fde
Author: Yi Pan (Data Infrastructure) <nickpan47@...>
Date: 2018-03-06T00:29:19Z
SAMZA-1600: remove the combination of cleanup policy "compact,delete" in
changelog topic properties
----
> Changelog topics for batch jobs should not use combination of delete+compact
> cleanup policy in Kafka
> ----------------------------------------------------------------------------------------------------
>
> Key: SAMZA-1600
> URL: https://issues.apache.org/jira/browse/SAMZA-1600
> Project: Samza
> Issue Type: Bug
> Reporter: Yi Pan (Data Infrastructure)
> Assignee: Yi Pan (Data Infrastructure)
> Priority: Major
>
> We have encountered a bug in Kafka 0.11 that when a topic is configured to
> use a combination of cleanup policy delete+compact, the broker enters a
> deadlock situation.
> Currently, we set the delete+compact policy for changelog topics in batch
> jobs to reduce the storage requirement and the additional GC effort required.
> However, before the above mentioned Kafka bug is fixed, we will disable this
> feature for now.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
