[
https://issues.apache.org/jira/browse/KAFKA-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-804:
--------------------------
Resolution: Fixed
Fix Version/s: 0.8
Status: Resolved (was: Patch Available)
Thanks for the review. Committed to 0.8 by addressing the following issues.
1. The stat for message rate is actually meant for monitoring data rates from
producers. So it's correct to only account for it in the leader during offset
assignment.
2. Fixed the log.
3. Fixed the issue with unnecessarily recreating the tuple.
4. Didn't fix count in analyzeAndValidateMessageSet in this patch. Will fix it
when merging to trunk. Will create a separate jira for review.
> Incorrect index in the log of a follower
> ----------------------------------------
>
> Key: KAFKA-804
> URL: https://issues.apache.org/jira/browse/KAFKA-804
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8
> Reporter: Jun Rao
> Assignee: Jun Rao
> Priority: Blocker
> Fix For: 0.8
>
> Attachments: kafka-804.patch
>
>
> In the follower, in log.append(), we use the offset of the 1st compressed
> message as the offset for appending index entries. This means that the index
> is pointing to an earlier position in the file than it should. Instead, it
> should use the offset of the 1st uncompressed message for appending index.
--
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
