[ https://issues.apache.org/jira/browse/KAFKA-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15043841#comment-15043841 ]
ASF GitHub Bot commented on KAFKA-1148: --------------------------------------- GitHub user iBuddha opened a pull request: https://github.com/apache/kafka/pull/633 KAFKA-1148 check leader epoch for DelayedProduce KAFKA-1148: check leader epoch for DelayedProduce You can merge this pull request into a Git repository by running: $ git pull https://github.com/iBuddha/kafka KAFKA-1148 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/633.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 #633 ---- commit 873b555906a773e19bdc3fc54fe9b3f5c3f8a6dd Author: xhuang <peopleb...@gmail.com> Date: 2015-12-06T12:02:49Z KAFKA-1148 check leader epoch for DelayedProduce ---- > Delayed fetch/producer requests should be satisfied on a leader change > ---------------------------------------------------------------------- > > Key: KAFKA-1148 > URL: https://issues.apache.org/jira/browse/KAFKA-1148 > Project: Kafka > Issue Type: Bug > Reporter: Joel Koshy > > Somewhat related to KAFKA-1016. > This would be an issue only if max.wait is set to a very high value. When a > leader change occurs we should remove the delayed request from the purgatory > - either satisfy with error/expire - whichever makes more sense. -- This message was sent by Atlassian JIRA (v6.3.4#6332)