[
https://issues.apache.org/jira/browse/KAFKA-6306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276635#comment-16276635
]
HongLiang commented on KAFKA-6306:
----------------------------------
[^_1085b605-f8f7-4df8-a13f-e0dd855179e4.png]
> Auto-commit of offsets fail, and not recover forever...
> -------------------------------------------------------
>
> Key: KAFKA-6306
> URL: https://issues.apache.org/jira/browse/KAFKA-6306
> Project: Kafka
> Issue Type: Bug
> Components: clients, consumer
> Affects Versions: 0.10.2.1, 1.0.0
> Reporter: HongLiang
> Labels: patch
> Attachments: _1085b605-f8f7-4df8-a13f-e0dd855179e4.png,
> _883ddf50-beb7-4e87-9630-168acaa9b046.png, auto-commit-fail-bugs.patch,
> e6cf53be-e128-47dc-a45a-79439a9e55ff.png,
> pool_46ba3275-7b56-4c64-a4f4-7280eb7f1728.png
>
>
> Auto-commit of offsets fail, and not recover forever. at
> sendOffsetCommitRequest, while "generation equal NULL", ConsumerCoordinator
> request will fail always. it maybe a bug. error log below:
> has more and more warn log ....
> "2017-12-01 22:08:39.112 WARN pool-390-thread-1#1
> (ConsumerCoordinator.java:626) - Auto-commit of offsets
> {drawing_gift_sent-1=OffsetAndMetadata{offset=32150359, metadata=''}} failed
> for group gift_rich_audience_write: Commit cannot be completed since the
> group has already rebalanced and assigned the partitions to another member.
> This means that the time between subsequent calls to poll() was longer than
> the configured max.poll.interval.ms, which typically implies that the poll
> loop is spending too much time message processing. You can address this
> either by increasing the session timeout or by reducing the maximum size of
> batches returned in poll() with max.poll.records."
> !e6cf53be-e128-47dc-a45a-79439a9e55ff.png|thumbnail!
> !_883ddf50-beb7-4e87-9630-168acaa9b046.png|thumbnail!
> !pool_46ba3275-7b56-4c64-a4f4-7280eb7f1728.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
