Kafka LEADER_NOT_AVAILABLE问题解决
来源:互联网 发布:优化布林线 编辑:程序博客网 时间:2024/05/25 19:59
[2017-10-30 19:05:18,410] WARN clients.NetworkClient: Error while fetching metadata with correlation id 49 : {BuB=LEADER_NOT_AVAILABLE}
[2017-10-30 19:05:18,516] WARN clients.NetworkClient: Error while fetching metadata with correlation id 50 : {BuB=LEADER_NOT_AVAILABLE}
[2017-10-30 19:05:18,622] WARN clients.NetworkClient: Error while fetching metadata with correlation id 51 : {BuB=LEADER_NOT_AVAILABLE}
[2017-10-30 19:05:18,731] WARN clients.NetworkClient: Error while fetching metadata with correlation id 52 : {BuB=LEADER_NOT_AVAILABLE}
[2017-10-30 19:05:18,837] WARN clients.NetworkClient: Error while fetching metadata with correlation id 53 : {BuB=LEADER_NOT_AVAILABLE}
[2017-10-30 19:05:18,946] WARN clients.NetworkClient: Error while fetching metadata with correlation id 54 : {BuB=LEADER_NOT_AVAILABLE}
[2017-10-30 19:05:19,053] WARN clients.NetworkClient: Error while fetching metadata with correlation id 55 : {BuB=LEADER_NOT_AVAILABLE}
[2017-10-30 19:05:19,161] WARN clients.NetworkClient: Error while fetching metadata with correlation id 56 : {BuB=LEADER_NOT_AVAILABLE}
[2017-10-30 19:05:18,516] WARN clients.NetworkClient: Error while fetching metadata with correlation id 50 : {BuB=LEADER_NOT_AVAILABLE}
[2017-10-30 19:05:18,622] WARN clients.NetworkClient: Error while fetching metadata with correlation id 51 : {BuB=LEADER_NOT_AVAILABLE}
[2017-10-30 19:05:18,731] WARN clients.NetworkClient: Error while fetching metadata with correlation id 52 : {BuB=LEADER_NOT_AVAILABLE}
[2017-10-30 19:05:18,837] WARN clients.NetworkClient: Error while fetching metadata with correlation id 53 : {BuB=LEADER_NOT_AVAILABLE}
[2017-10-30 19:05:18,946] WARN clients.NetworkClient: Error while fetching metadata with correlation id 54 : {BuB=LEADER_NOT_AVAILABLE}
[2017-10-30 19:05:19,053] WARN clients.NetworkClient: Error while fetching metadata with correlation id 55 : {BuB=LEADER_NOT_AVAILABLE}
[2017-10-30 19:05:19,161] WARN clients.NetworkClient: Error while fetching metadata with correlation id 56 : {BuB=LEADER_NOT_AVAILABLE}
[2017-10-30 19:05:19,268] WARN clients.NetworkClient: Error while fetching metadata with correlation id 57 : {BuB=LEADER_NOT_AVAILABLE}
删除Zookeeper 的Broker解决:客户端登录zookeeper,输入命令 rmr /brokers
阅读全文
0 0
- Kafka LEADER_NOT_AVAILABLE问题解决
- Kafka_2.10-0.10.0.0- LEADER_NOT_AVAILABLE
- Kafka ConsumerOffsetChecker 命令失效问题解决
- windows kafka安装及问题解决
- kafka Failed to send messages after 3 tries 问题解决
- kafka Failed to send messages after 3 tries 问题解决。
- Kafka“Failed to send messages after 3 tries”问题解决
- Kafka集群无法外网访问问题解决攻略
- Kafka集群无法外网访问问题解决攻略
- kafka java中发送数据、连接失败问题解决
- Kafka
- kafka
- kafka
- KAFKA
- Kafka
- kafka
- kafka
- kafka
- js获取手机ip
- easyui加载combobox
- 链表问题 在单链表和双链表中删除倒数第K个节点
- 3Sum
- Linux网络编程--(1)网络体系架构
- Kafka LEADER_NOT_AVAILABLE问题解决
- HTTP请求行、请求头、请求体详解
- 多个按钮调用同一个方法
- HDU4069-Squiggly Sudoku
- 超前-滞后型DPLL提取位同步时钟的FPGA实现
- LeetCode 452 射气球问题
- SSL2810 2017年10月30日提高组T2 数论(math)
- MapReduce MapTask任务数量,切片大小笔记
- Leetcode 645 FindErrorNum