国产无码综合区,色欲AV无码国产永久播放,无码天堂亚洲国产AV,国产日韩欧美女同一区二区

<b id="xenhu"></b>

kafka-報錯-The coordinator is not aware of this member

2年前作者：背風(fēng)衣人分類：Toy博客閱讀(18)違法舉報

這篇具有很好參考價值的文章主要介紹了kafka-報錯-The coordinator is not aware of this member。希望對大家有所幫助。如果存在錯誤或未考慮完全的地方，請大家不吝賜教，您也可以點擊"舉報違法"按鈕提交疑問。

問題描述

我在項目里把原來用著的獨立消費(fèi)者 consumer-group-id 同時當(dāng)做消費(fèi)者組來消費(fèi)分區(qū)信息，導(dǎo)致協(xié)調(diào)器找不到這個 consumer-group-id

2022-12-14 16:33:31.908 ERROR 16020 --- [ntainer#0-0-C-1] o.a.k.c.c.internals.ConsumerCoordinator  : [Consumer clientId=consumer-spring-kafka-evo-consumer-001-9, groupId=spring-kafka-evo-consumer-001] Offset commit failed on partition REBALANCE-ONE-TOPIC-1 at offset 13: The coordinator is not aware of this member.
2022-12-14 16:33:31.908  INFO 16020 --- [ntainer#0-0-C-1] o.a.k.c.c.internals.ConsumerCoordinator  : [Consumer clientId=consumer-spring-kafka-evo-consumer-001-9, groupId=spring-kafka-evo-consumer-001] OffsetCommit failed with Generation{generationId=-1, memberId='', protocol='null'}: The coordinator is not aware of this member.
2022-12-14 16:33:31.908  INFO 16020 --- [ntainer#0-0-C-1] o.a.k.c.c.internals.ConsumerCoordinator  : [Consumer clientId=consumer-spring-kafka-evo-consumer-001-9, groupId=spring-kafka-evo-consumer-001] Resetting generation due to: encountered UNKNOWN_MEMBER_ID from OFFSET_COMMIT response
2022-12-14 16:33:31.908  INFO 16020 --- [ntainer#0-0-C-1] o.a.k.c.c.internals.ConsumerCoordinator  : [Consumer clientId=consumer-spring-kafka-evo-consumer-001-9, groupId=spring-kafka-evo-consumer-001] Request joining group due to: encountered UNKNOWN_MEMBER_ID from OFFSET_COMMIT response
2022-12-14 16:33:31.909 ERROR 16020 --- [ntainer#0-0-C-1] o.s.k.l.KafkaMessageListenerContainer    : Consumer exception

java.lang.IllegalStateException: This error handler cannot process 'org.apache.kafka.clients.consumer.CommitFailedException's; no record information is available
	at org.springframework.kafka.listener.DefaultErrorHandler.handleOtherException(DefaultErrorHandler.java:157) ~[spring-kafka-2.8.9.jar:2.8.9]
	at org.springframework.kafka.listener.KafkaMessageListenerContainer$ListenerConsumer.handleConsumerException(KafkaMessageListenerContainer.java:1812) [spring-kafka-2.8.9.jar:2.8.9]
	at org.springframework.kafka.listener.KafkaMessageListenerContainer$ListenerConsumer.run(KafkaMessageListenerContainer.java:1301) [spring-kafka-2.8.9.jar:2.8.9]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_251]
	at java.util.concurrent.FutureTask.run$$$capture(FutureTask.java:266) [na:1.8.0_251]
	at java.util.concurrent.FutureTask.run(FutureTask.java) [na:1.8.0_251]
	at java.lang.Thread.run(Thread.java:748) [na:1.8.0_251]
Caused by: org.apache.kafka.clients.consumer.CommitFailedException: 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 max.poll.interval.ms or by reducing the maximum size of batches returned in poll() with max.poll.records.
	at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator$OffsetCommitResponseHandler.handle(ConsumerCoordinator.java:1303) ~[kafka-clients-3.1.2.jar:na]
	at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator$OffsetCommitResponseHandler.handle(ConsumerCoordinator.java:1204) ~[kafka-clients-3.1.2.jar:na]
	at org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:1196) ~[kafka-clients-3.1.2.jar:na]
	at org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:1171) ~[kafka-clients-3.1.2.jar:na]
	at org.apache.kafka.clients.consumer.internals.RequestFuture$1.onSuccess(RequestFuture.java:206) ~[kafka-clients-3.1.2.jar:na]
	at org.apache.kafka.clients.consumer.internals.RequestFuture.fireSuccess(RequestFuture.java:169) ~[kafka-clients-3.1.2.jar:na]
	at org.apache.kafka.clients.consumer.internals.RequestFuture.complete(RequestFuture.java:129) ~[kafka-clients-3.1.2.jar:na]
	at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient$RequestFutureCompletionHandler.fireCompletion(ConsumerNetworkClient.java:602) ~[kafka-clients-3.1.2.jar:na]
	at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.firePendingCompletedRequests(ConsumerNetworkClient.java:412) ~[kafka-clients-3.1.2.jar:na]
	at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:297) ~[kafka-clients-3.1.2.jar:na]
	at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:236) ~[kafka-clients-3.1.2.jar:na]
	at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:215) ~[kafka-clients-3.1.2.jar:na]
	at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.commitOffsetsSync(ConsumerCoordinator.java:1046) ~[kafka-clients-3.1.2.jar:na]
	at org.apache.kafka.clients.consumer.KafkaConsumer.commitSync(KafkaConsumer.java:1492) ~[kafka-clients-3.1.2.jar:na]
	at org.springframework.kafka.listener.KafkaMessageListenerContainer$ListenerConsumer.doCommitSync(KafkaMessageListenerContainer.java:3062) [spring-kafka-2.8.9.jar:2.8.9]
	at org.springframework.kafka.listener.KafkaMessageListenerContainer$ListenerConsumer.commitSync(KafkaMessageListenerContainer.java:3057) [spring-kafka-2.8.9.jar:2.8.9]
	at org.springframework.kafka.listener.KafkaMessageListenerContainer$ListenerConsumer.commitIfNecessary(KafkaMessageListenerContainer.java:3043) [spring-kafka-2.8.9.jar:2.8.9]
	at org.springframework.kafka.listener.KafkaMessageListenerContainer$ListenerConsumer.processCommits(KafkaMessageListenerContainer.java:2835) [spring-kafka-2.8.9.jar:2.8.9]
	at org.springframework.kafka.listener.KafkaMessageListenerContainer$ListenerConsumer.pollAndInvoke(KafkaMessageListenerContainer.java:1329) [spring-kafka-2.8.9.jar:2.8.9]
	at org.springframework.kafka.listener.KafkaMessageListenerContainer$ListenerConsumer.run(KafkaMessageListenerContainer.java:1255) [spring-kafka-2.8.9.jar:2.8.9]
	... 4 common frames omitted

報錯復(fù)現(xiàn)方式

注冊兩個測試 topic

    @Bean
    public NewTopic testone() {
        return TopicBuilder.name("test-topic-group").partitions(2).replicas(1).build();
    }

    @Bean
    public NewTopic testtwo() {
        return TopicBuilder.name("test-topic-standalone").partitions(1).replicas(1).build();
    }

寫一個消費(fèi)者組


import lombok.extern.slf4j.Slf4j;
import org.springframework.kafka.annotation.KafkaListener;
import org.springframework.kafka.annotation.PartitionOffset;
import org.springframework.kafka.annotation.TopicPartition;
import org.springframework.stereotype.Component;

@Component
@Slf4j
public class TestErrorConsumerListener {

    /**
     * 消費(fèi)者組
     */
    @KafkaListener(groupId = "test-group", topicPartitions = {
        @TopicPartition(topic = "test-topic-group", partitions = "0", partitionOffsets = @PartitionOffset(partition = "*", initialOffset = "0"))
    })
    public void one(String value) {
        log.info("one：接收kafka消息：[{}]", value);
    }

    /**
     * 消費(fèi)者組
     */
    @KafkaListener(groupId = "test-group", topicPartitions = {
        @TopicPartition(topic = "test-topic-group", partitions = "1", partitionOffsets = @PartitionOffset(partition = "*", initialOffset = "0"))
    })
    public void two(String value) {
        log.info("two：接收kafka消息：[{}]", value);
    }

    /**
     * 獨立消費(fèi)者
     */
    @KafkaListener(topics = "test-topic-standalone", groupId = "test-group")
    public void three(String value) {
        log.info("three：接收kafka消息：[{}]", value);
    }
}

啟動項目，發(fā)送消息

this.template.send("test-topic-group", message);
this.template.send("test-topic-standalone", message);

報錯日志

2022-12-14 19:04:18.835  INFO 13416 --- [tainer#13-0-C-1] c.l.p.e.k.c.TestErrorConsumerListener    : one：接收kafka消息：[111111111]
2022-12-14 19:04:18.841  INFO 13416 --- [tainer#14-0-C-1] c.l.p.e.k.c.TestErrorConsumerListener    : three：接收kafka消息：[111111111]
2022-12-14 19:04:19.336  INFO 13416 --- [tainer#13-0-C-1] o.a.k.c.c.internals.ConsumerCoordinator  : [Consumer clientId=consumer-test-group-15, groupId=test-group] Discovered group coordinator 192.168.136.136:9092 (id: 2147482646 rack: null)
2022-12-14 19:04:19.338 ERROR 13416 --- [tainer#13-0-C-1] o.a.k.c.c.internals.ConsumerCoordinator  : [Consumer clientId=consumer-test-group-15, groupId=test-group] Offset commit failed on partition test-topic-group-0 at offset 1: The coordinator is not aware of this member.
2022-12-14 19:04:19.338  INFO 13416 --- [tainer#13-0-C-1] o.a.k.c.c.internals.ConsumerCoordinator  : [Consumer clientId=consumer-test-group-15, groupId=test-group] OffsetCommit failed with Generation{generationId=-1, memberId='', protocol='null'}: The coordinator is not aware of this member.
2022-12-14 19:04:19.338  INFO 13416 --- [tainer#13-0-C-1] o.a.k.c.c.internals.ConsumerCoordinator  : [Consumer clientId=consumer-test-group-15, groupId=test-group] Resetting generation due to: encountered UNKNOWN_MEMBER_ID from OFFSET_COMMIT response
2022-12-14 19:04:19.338  INFO 13416 --- [tainer#13-0-C-1] o.a.k.c.c.internals.ConsumerCoordinator  : [Consumer clientId=consumer-test-group-15, groupId=test-group] Request joining group due to: encountered UNKNOWN_MEMBER_ID from OFFSET_COMMIT response
2022-12-14 19:04:19.342 ERROR 13416 --- [tainer#13-0-C-1] o.s.k.l.KafkaMessageListenerContainer    : Consumer exception

java.lang.IllegalStateException: This error handler cannot process 'org.apache.kafka.clients.consumer.CommitFailedException's; no record information is available
	at org.springframework.kafka.listener.DefaultErrorHandler.handleOtherException(DefaultErrorHandler.java:157) ~[spring-kafka-2.8.9.jar:2.8.9]
	at org.springframework.kafka.listener.KafkaMessageListenerContainer$ListenerConsumer.handleConsumerException(KafkaMessageListenerContainer.java:1812) [spring-kafka-2.8.9.jar:2.8.9]
	at org.springframework.kafka.listener.KafkaMessageListenerContainer$ListenerConsumer.run(KafkaMessageListenerContainer.java:1301) [spring-kafka-2.8.9.jar:2.8.9]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_251]
	at java.util.concurrent.FutureTask.run$$$capture(FutureTask.java:266) [na:1.8.0_251]
	at java.util.concurrent.FutureTask.run(FutureTask.java) [na:1.8.0_251]
	at java.lang.Thread.run(Thread.java:748) [na:1.8.0_251]
Caused by: org.apache.kafka.clients.consumer.CommitFailedException: 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 max.poll.interval.ms or by reducing the maximum size of batches returned in poll() with max.poll.records.
	at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator$OffsetCommitResponseHandler.handle(ConsumerCoordinator.java:1303) ~[kafka-clients-3.1.2.jar:na]
	at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator$OffsetCommitResponseHandler.handle(ConsumerCoordinator.java:1204) ~[kafka-clients-3.1.2.jar:na]
	at org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:1196) ~[kafka-clients-3.1.2.jar:na]
	at org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:1171) ~[kafka-clients-3.1.2.jar:na]
	at org.apache.kafka.clients.consumer.internals.RequestFuture$1.onSuccess(RequestFuture.java:206) ~[kafka-clients-3.1.2.jar:na]
	at org.apache.kafka.clients.consumer.internals.RequestFuture.fireSuccess(RequestFuture.java:169) ~[kafka-clients-3.1.2.jar:na]
	at org.apache.kafka.clients.consumer.internals.RequestFuture.complete(RequestFuture.java:129) ~[kafka-clients-3.1.2.jar:na]
	at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient$RequestFutureCompletionHandler.fireCompletion(ConsumerNetworkClient.java:602) ~[kafka-clients-3.1.2.jar:na]
	at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.firePendingCompletedRequests(ConsumerNetworkClient.java:412) ~[kafka-clients-3.1.2.jar:na]
	at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:297) ~[kafka-clients-3.1.2.jar:na]
	at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:236) ~[kafka-clients-3.1.2.jar:na]
	at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:215) ~[kafka-clients-3.1.2.jar:na]
	at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.commitOffsetsSync(ConsumerCoordinator.java:1046) ~[kafka-clients-3.1.2.jar:na]
	at org.apache.kafka.clients.consumer.KafkaConsumer.commitSync(KafkaConsumer.java:1492) ~[kafka-clients-3.1.2.jar:na]
	at org.springframework.kafka.listener.KafkaMessageListenerContainer$ListenerConsumer.doCommitSync(KafkaMessageListenerContainer.java:3062) [spring-kafka-2.8.9.jar:2.8.9]
	at org.springframework.kafka.listener.KafkaMessageListenerContainer$ListenerConsumer.commitSync(KafkaMessageListenerContainer.java:3057) [spring-kafka-2.8.9.jar:2.8.9]
	at org.springframework.kafka.listener.KafkaMessageListenerContainer$ListenerConsumer.commitIfNecessary(KafkaMessageListenerContainer.java:3043) [spring-kafka-2.8.9.jar:2.8.9]
	at org.springframework.kafka.listener.KafkaMessageListenerContainer$ListenerConsumer.processCommits(KafkaMessageListenerContainer.java:2835) [spring-kafka-2.8.9.jar:2.8.9]
	at org.springframework.kafka.listener.KafkaMessageListenerContainer$ListenerConsumer.pollAndInvoke(KafkaMessageListenerContainer.java:1329) [spring-kafka-2.8.9.jar:2.8.9]
	at org.springframework.kafka.listener.KafkaMessageListenerContainer$ListenerConsumer.run(KafkaMessageListenerContainer.java:1255) [spring-kafka-2.8.9.jar:2.8.9]
	... 4 common frames omitted

查看kafka服務(wù)器的消費(fèi)者狀態(tài)文章來源地址http://www.zghlxwxcb.cn/news/detail-543640.html

$KAFKA_HOME/bin/kafka-consumer-groups.sh --bootstrap-server 127.0.0.1:9092 --group test-group --describe


GROUP           TOPIC                 PARTITION  CURRENT-OFFSET  LOG-END-OFFSET  LAG             CONSUMER-ID                                                 HOST            CLIENT-ID
test-group      test-topic-standalone 0          1               1               0               consumer-test-group-16-d1a0c068-a68d-456c-a958-97b44219ef1b /192.168.136.1  consumer-test-group-16

到了這里，關(guān)于kafka-報錯-The coordinator is not aware of this member的文章就介紹完了。如果您還想了解更多內(nèi)容，請在右上角搜索TOY模板網(wǎng)以前的文章或繼續(xù)瀏覽下面的相關(guān)文章，希望大家以后多多支持TOY模板網(wǎng)！

本文來自互聯(lián)網(wǎng)用戶投稿，該文觀點僅代表作者本人，不代表本站立場。本站僅提供信息存儲空間服務(wù)，不擁有所有權(quán)，不承擔(dān)相關(guān)法律責(zé)任。如若轉(zhuǎn)載，請注明出處：如若內(nèi)容造成侵權(quán)/違法違規(guī)/事實不符，請點擊違法舉報進(jìn)行投訴反饋，一經(jīng)查實，立即刪除！

分享到：

領(lǐng)支付寶紅包贊助服務(wù)器費(fèi)用

this Docker version is not on the list of validated versions: 24.0.7. Latest validated version: 20.1
報錯信息可以看出跟docker的版本有關(guān)系，意思是：此 Docker 版本不在已驗證版本列表中： 24.0.7 。最新驗證版本： 20.10 降低docker版本到20.10 1、查看當(dāng)前倉庫支持的docker版本 yum list docker-ce --showduplicates | sort -r 2、降低docker版本到3:20.10.9-3.el8 語法： yum downgrade --setopt=obsoletes=0
2024年01月18日
瀏覽(22)
Error: The user of this service-type is not allowed to use a reversible encryption algorithm
在交換機(jī)或者路由器進(jìn)行AAA認(rèn)證時，修改用戶密碼出現(xiàn)以下狀況改如何解決“Error: The user of this service-type is not allowed to use a reversible encryption algorithm”。配置local-user 用戶名 password cipher報錯.....--此時需要把cipher換成irreversible-cipher。于是，重新連接交換機(jī)修改密碼，換個命令
2024年02月14日
瀏覽(20)
解決Docker報錯：This error may indicate that the docker daemon is not running.
? ? ? ?成功安裝完docker【安裝過程見上一篇Windows安裝docker_up_xin的博客-CSDN博客】后的第二天就遇到了問題，進(jìn)入PowerShell后報錯如下： ? ? ? 網(wǎng)上常見的解決方法是在Service Windows GUI重啟docker desktop service，或者使用?DockerCli.exe -SwitchDaemon命令，但是都沒能解決 ????????網(wǎng)
2024年02月11日
瀏覽(20)
Failed to execute ‘removeChild‘ on ‘Node‘: The node to be removed is not a child of this node.
在React項目開發(fā)的時候遇到了這種報錯，曾經(jīng)百思不得其解。之前一個表格的時候都是好好的，但是這次用了tabs切換兩個表格之后就出現(xiàn)了這個問題... 發(fā)現(xiàn)問題的操作就是：頁面刷新之后直接點擊tabs默認(rèn)顯示的表格中的某個單元格就直接報錯了。可能是如下報錯信息，這個
2024年02月12日
瀏覽(23)
THE SELF PRESERVATION MODE IS TURNED OFF.THIS MAY NOT PROTECT INSTANCE EXPIRY IN CASE OF NETWORK/OTH
?
2024年02月13日
瀏覽(19)
解決報錯The JAVA_HOME environment variable is not defined correctly This environment variable is needed
注：本方法適用于安裝過java的用戶一、報錯內(nèi)容：在使用mvn命令時，環(huán)境變量報錯：二、查看環(huán)境變量后發(fā)現(xiàn)jdk路徑錯誤,可是我jdk重裝過，想不起來怎么辦？我在命令行窗口使用java -verbose查出來的路徑為： E:/java/bin 但是當(dāng)我興高采烈在環(huán)境變量設(shè)置中寫入此環(huán)境變量后
2024年02月03日
瀏覽(24)
maven配置報錯The JAVA_HOME environment variable is not defined correctly,this environment variable is
1.問題原因 2.參考文檔
2024年02月16日
瀏覽(44)
npm v10.0.0 is known not to run on Node.js v12.8.0. This version of npm supports the following node
執(zhí)行命令時報錯：ERROR: npm vxxx is known not to run on Node.js vxxx. ?This version of npm supports the following node versions: `^18.17.0 || =20.5.0`. You can find the latest version at https://nodejs.org/. 報錯說你現(xiàn)在的npm版本是vxxx 不支持你現(xiàn)在Node的版本vxxx，需要把node版本改成npm支持的版本，在node官網(wǎng)你可以找
2024年02月08日
瀏覽(26)
kafka消費(fèi)者報錯Offset commit ......it is likely that the consumer was kicked out of the group的解決
2022年10月份接到一個小功能，對接kafka將數(shù)據(jù)寫到數(shù)據(jù)庫，開始的需求就是無腦批量insert，隨著時間的推移，業(yè)務(wù)需求有變更，kafka的生產(chǎn)消息頻次越來越高，到今年7月份為止就每秒會有幾十條甚至上百條，然后消費(fèi)消息的代碼就報錯： Caused by: org.apache.kafka.clients.consumer.Com
2024年02月07日
瀏覽(23)
PerformanceWarning: DataFrame is highly fragmented. This is usually the result of calling frame.inse
對DataFrame的數(shù)據(jù)進(jìn)行添加時，數(shù)據(jù)量過多而造成的，雖然結(jié)果還是有的，但是一直報錯，很煩問題代碼：代碼所示，我想做機(jī)器學(xué)習(xí)訓(xùn)練的時候，簡單做一下數(shù)據(jù)增強(qiáng)，就直接搞了一個for循環(huán)，因為數(shù)據(jù)量過大顯示出錯解決方法如下 1、先用新的字典把數(shù)據(jù)增強(qiáng)部分的數(shù)據(jù)
2024年02月16日
瀏覽(13)