[
https://issues.apache.org/jira/browse/KAFKA-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15120954#comment-15120954
]
ASF GitHub Bot commented on KAFKA-3157:
---------------------------------------
GitHub user xiaotao183 opened a pull request:
https://github.com/apache/kafka/pull/821
KAFKA-3157 - Mirror maker doesn't commit offset
Mirror maker doesn't commit offset with new consumer enabled when data
volume is low. This is caused by infinite loop in ```receive()``` which would
never jump out of loop if no data coming
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/xiaotao183/kafka KAFKA-3157
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/821.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 #821
----
commit c3221c0d0391080889ab899f8570b629561a8529
Author: Tao Xiao <[email protected]>
Date: 2016-01-28T07:42:27Z
KAFKA-3157 - Mirror maker doesn't commit offset with new consumer enabled
if data volume is low
----
> Mirror maker doesn't commit offset with new consumer when there is no more
> messages
> -----------------------------------------------------------------------------------
>
> Key: KAFKA-3157
> URL: https://issues.apache.org/jira/browse/KAFKA-3157
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.9.0.0
> Reporter: TAO XIAO
> Assignee: TAO XIAO
>
> Mirror maker doesn't commit messages with new consumer enabled when messages
> are sent to source within the time range that is smaller than commit interval
> and no more messages are sent afterwards.
> The steps to reproduce:
> 1. Start mirror maker.
> 2. The default commit interval is 1 min. Send message for less than 1 min for
> example 10 seconds.
> 3. Don't send more messages.
> 4. Check committed offset with group command. The lag remains unchanged for
> ever even though the messages have been sent to destination.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
