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 2012/10/16 06:29:05 UTC

[jira] [Closed] (KAFKA-557) Replica fetch thread doesn't need to recompute message id

     [ https://issues.apache.org/jira/browse/KAFKA-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jun Rao closed KAFKA-557.
-------------------------

    
> Replica fetch thread doesn't need to recompute message id
> ---------------------------------------------------------
>
>                 Key: KAFKA-557
>                 URL: https://issues.apache.org/jira/browse/KAFKA-557
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.8
>            Reporter: Jun Rao
>            Assignee: Jay Kreps
>            Priority: Blocker
>              Labels: bugs
>             Fix For: 0.8
>
>         Attachments: KAFKA-557.patch, KAFKA-557.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> With kafka-506, the leader broker computes the logical id for each message produced. This could involve decompressing and recompressing messages, which are expensive. When data is replicated from the leader to the follower, we could avoid recomputing the logical message id since it's the same.

--
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