You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Bill Bejeck (Jira)" <ji...@apache.org> on 2020/12/10 19:08:00 UTC
[jira] [Comment Edited] (KAFKA-10802) Spurious log message when
starting consumers
[ https://issues.apache.org/jira/browse/KAFKA-10802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17247431#comment-17247431 ]
Bill Bejeck edited comment on KAFKA-10802 at 12/10/20, 7:07 PM:
----------------------------------------------------------------
Thanks for the heads up [~mimaison] I need to do a new RC for 2.7.0 anyway so I'll include this as well. -Is there a merged PR already-? NM I failed to read all the comments and I see that [~guozhang] has merged something into trunk.
was (Author: bbejeck):
Thanks for the heads up [~mimaison] I need to do a new RC for 2.7.0 anyway so I'll include this. Is there a merged PR already?
> Spurious log message when starting consumers
> --------------------------------------------
>
> Key: KAFKA-10802
> URL: https://issues.apache.org/jira/browse/KAFKA-10802
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 2.6.0
> Reporter: Mickael Maison
> Priority: Major
>
> Reported by Gary Russell in the [2.6.1 RC3 vote thread|https://lists.apache.org/thread.html/r13d2c687b2fafbe9907fceb3d4f3cc6d5b34f9f36a7fcc985c38b506%40%3Cdev.kafka.apache.org%3E]
> I am seeing this on every consumer start:
> 2020-11-25 13:54:34.858 INFO 42250 --- [ntainer#0-0-C-1] o.a.k.c.c.internals.AbstractCoordinator : [Consumer clientId=consumer-ktest26int-1, groupId=ktest26int] Rebalance failed.
> org.apache.kafka.common.errors.MemberIdRequiredException: The group member needs to have a valid member id before actually entering a consumer group.
> Due to this change https://github.com/apache/kafka/commit/16ec1793d53700623c9cb43e711f585aafd44dd4#diff-15efe9b844f78b686393b6c2e2ad61306c3473225742caed05c7edab9a138832R468
> I understand what a MemberIdRequiredException is, but the previous (2.6.0) log (with exception.getMessage()) didn't stand out like the new one does because it was all on one line.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)