You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jun Rao (JIRA)" <ji...@apache.org> on 2013/03/13 05:40:13 UTC

[jira] [Commented] (KAFKA-802) Flush message interval is based on compressed message count

    [ https://issues.apache.org/jira/browse/KAFKA-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13600809#comment-13600809 ] 

Jun Rao commented on KAFKA-802:
-------------------------------

This is easy to fix on the leader since it iterates uncompressed messages to assign offsets. It's a bit hard to fix in the follower. We could iterate uncompressed messages. This will add CPU overhead though.
                
> Flush message interval is based on compressed message count
> -----------------------------------------------------------
>
>                 Key: KAFKA-802
>                 URL: https://issues.apache.org/jira/browse/KAFKA-802
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.8
>            Reporter: Jun Rao
>            Priority: Blocker
>
> In Log.append(), we use compressed message count to determine whether to flush the log or not. We should use uncompressed message count instead.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira