[
https://issues.apache.org/jira/browse/KAFKA-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14141179#comment-14141179
]
Guozhang Wang commented on KAFKA-1640:
--------------------------------------
[~chenshangan...@163.com],[~jkreps] for this message-size-too-large particular
case, currently the broker will only silently return no data, and the fetcher
thread does not know there is any problems happened. To resolve this we can let
broker to return an error-code in this case to notify the consumer.
A more general problem for the old consumer is that since it is not single
threaded, and issues exposed in the background fetcher thread may not be easily
exposed to the caller thread. We will fix this issue in the new consumer, and I
will file a sub-ticket for the new consumer project to add message-too-large
error code for fetch response.
> consumer will fail if encounter special offset
> ----------------------------------------------
>
> Key: KAFKA-1640
> URL: https://issues.apache.org/jira/browse/KAFKA-1640
> Project: Kafka
> Issue Type: Bug
> Components: consumer
> Affects Versions: 0.8.1.1
> Reporter: chenshangan
> Assignee: Neha Narkhede
>
> I'm running topology on storm which consume messages from kafka. Sometimes I
> encounter exceptions like offset out of range. I did not pay much attention
> on this problem before and just restarted the topology to consume messages
> from latest offset because of various reasons. Recently, more services are
> dependent on kafka, and this problem still exists. According to the invalid
> offset information, I did a test and finally found the problem. There exists
> an offset which consumer can never start from and can not skip over it unless
> you provide next valid offset to start from. I can not figure out why.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
