Linux系统Kafka集群搭建与简单测试-白红宇

Linux系统Kafka集群搭建与简单测试

阅读量：6909 次

发布时间：2019-06-27

本文共 21023 字，大约阅读时间需要 70 分钟。

Kafka安装

Zookeeper集群搭建，可参考

上传kafka安装包并解压

[root@localhost ~]# cd /home/listen[root@localhost listen]# lltotal 8drwxr-xr-x.  3 listen listen   23 Apr 27 01:48 codisdrwxr-xr-x.  3 root   root     19 May 18 19:37 dubboxdrwxrwxr-x.  3 listen listen   48 Apr 26 20:16 godrwxrwxr-x.  4 listen listen   64 May 13 03:14 gradledrwxrwxr-x.  2 listen listen   35 Apr 26 19:53 jdkdrwxr-xr-x.  3 root   root     64 May 18 18:46 mavendrwxrwxr-x.  4 listen listen  100 May  3 00:52 nginxdrwxrwxr-x.  4 listen listen   66 Apr 26 19:31 redisdrwxrwxr-x.  3 listen listen   94 May 10 00:42 sessiondrwxrwxr-x.  4 listen listen 4096 May 10 17:58 tomcatdrwxrwxr-x. 10 listen listen 4096 May 11 03:22 zookeeper[root@localhost listen]# mkdir kafka[root@localhost listen]# cd kafka/[root@localhost kafka]# lltotal 30840-rw-r--r--. 1 root root 31579147 May 30 00:36 kafka_2.11-0.10.0.0.tgz[root@localhost kafka]# tar -xvf kafka_2.11-0.10.0.0.tgz

编辑配置文件

[root@localhost config]# pwd/home/listen/kafka/kafka_2.11-0.10.0.0/config[root@localhost config]# lsconnect-console-sink.properties    connect-file-sink.properties    connect-standalone.properties  producer.properties     zookeeper.propertiesconnect-console-source.properties  connect-file-source.properties  consumer.properties            server.propertiesconnect-distributed.properties     connect-log4j.properties        log4j.properties               tools-log4j.properties[root@localhost config]# vi server.properties

这个是server.properties文件内容

# Licensed to the Apache Software Foundation (ASF) under one or more# contributor license agreements.  See the NOTICE file distributed with# this work for additional information regarding copyright ownership.# The ASF licenses this file to You under the Apache License, Version 2.0# (the "License"); you may not use this file except in compliance with# the License.  You may obtain a copy of the License at##    http://www.apache.org/licenses/LICENSE-2.0## Unless required by applicable law or agreed to in writing, software# distributed under the License is distributed on an "AS IS" BASIS,# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.# See the License for the specific language governing permissions and# limitations under the License.# see kafka.server.KafkaConfig for additional details and defaults############################# Server Basics ############################## The id of the broker. This must be set to a unique integer for each broker.broker.id=0############################# Socket Server Settings ############################## The address the socket server listens on. It will get the value returned from # java.net.InetAddress.getCanonicalHostName() if not configured.#   FORMAT:#     listeners = security_protocol://host_name:port#   EXAMPLE:#     listeners = PLAINTEXT://your.host.name:9092listeners=PLAINTEXT://:9092# Hostname and port the broker will advertise to producers and consumers. If not set, # it uses the value for "listeners" if configured.  Otherwise, it will use the value# returned from java.net.InetAddress.getCanonicalHostName().#advertised.listeners=PLAINTEXT://your.host.name:9092advertised.listeners=PLAINTEXT://192.168.75.141:9092port=9092host.name=192.168.75.141advertised.host.name=192.168.75.141advertised.port=9092# The number of threads handling network requestsnum.network.threads=3# The number of threads doing disk I/Onum.io.threads=8# The send buffer (SO_SNDBUF) used by the socket serversocket.send.buffer.bytes=102400# The receive buffer (SO_RCVBUF) used by the socket serversocket.receive.buffer.bytes=102400# The maximum size of a request that the socket server will accept (protection against OOM)socket.request.max.bytes=104857600############################# Log Basics ############################## A comma seperated list of directories under which to store log fileslog.dirs=/home/listen/kafka/kafka_2.11-0.10.0.0/logs/server0# The default number of log partitions per topic. More partitions allow greater# parallelism for consumption, but this will also result in more files across# the brokers.num.partitions=1# The number of threads per data directory to be used for log recovery at startup and flushing at shutdown.# This value is recommended to be increased for installations with data dirs located in RAID array.num.recovery.threads.per.data.dir=1############################# Log Flush Policy ############################## Messages are immediately written to the filesystem but by default we only fsync() to sync# the OS cache lazily. The following configurations control the flush of data to disk.# There are a few important trade-offs here:#    1. Durability: Unflushed data may be lost if you are not using replication.#    2. Latency: Very large flush intervals may lead to latency spikes when the flush does occur as there will be a lot of data to flush.#    3. Throughput: The flush is generally the most expensive operation, and a small flush interval may lead to exceessive seeks.# The settings below allow one to configure the flush policy to flush data after a period of time or# every N messages (or both). This can be done globally and overridden on a per-topic basis.# The number of messages to accept before forcing a flush of data to disk#log.flush.interval.messages=10000# The maximum amount of time a message can sit in a log before we force a flush#log.flush.interval.ms=1000############################# Log Retention Policy ############################## The following configurations control the disposal of log segments. The policy can# be set to delete segments after a period of time, or after a given size has accumulated.# A segment will be deleted whenever *either* of these criteria are met. Deletion always happens# from the end of the log.# The minimum age of a log file to be eligible for deletionlog.retention.hours=168# A size-based retention policy for logs. Segments are pruned from the log as long as the remaining# segments don't drop below log.retention.bytes.#log.retention.bytes=1073741824# The maximum size of a log segment file. When this size is reached a new log segment will be created.log.segment.bytes=1073741824# The interval at which log segments are checked to see if they can be deleted according# to the retention policieslog.retention.check.interval.ms=300000############################# Zookeeper ############################## Zookeeper connection string (see zookeeper docs for details).# This is a comma separated host:port pairs, each corresponding to a zk# server. e.g. "127.0.0.1:3000,127.0.0.1:3001,127.0.0.1:3002".# You can also append an optional chroot string to the urls to specify the# root directory for all kafka znodes.zookeeper.connect=192.168.75.141:2181,192.168.75.141:2182,192.168.75.141:2183,192.168.75.141:2184,192.168.75.141:2185# Timeout in ms for connecting to zookeeperzookeeper.connection.timeout.ms=6000

增加集群的配置文件server1.properties

[root@localhost config]# cp server.properties server1.properties [root@localhost config]# vi server1.properties

修改配置

broker.id=1listeners=PLAINTEXT://:9093advertised.listeners=PLAINTEXT://192.168.75.141:9093port=9093host.name=192.168.75.141advertised.host.name=192.168.75.141advertised.port=9093log.dirs=/home/listen/kafka/kafka_2.11-0.10.0.0/logs/server1#其他配置和server.properties一样

增加集群的配置文件server2.properties

[root@localhost config]# cp server.properties server2.properties [root@localhost config]# vi server2.properties

修改配置

broker.id=2listeners=PLAINTEXT://:9094advertised.listeners=PLAINTEXT://192.168.75.141:9094port=9094host.name=192.168.75.141advertised.host.name=192.168.75.141advertised.port=9094log.dirs=/home/listen/kafka/kafka_2.11-0.10.0.0/logs/server2#其他配置和server.properties一样

[root@localhost ~]# cd /home/listen/kafka/[root@localhost kafka]# lltotal 30840drwxr-xr-x. 6 root root       83 May 17 21:32 kafka_2.11-0.10.0.0-rw-r--r--. 1 root root 31579147 May 30 00:36 kafka_2.11-0.10.0.0.tgz[root@localhost kafka]# cd kafka_2.11-0.10.0.0/[root@localhost kafka_2.11-0.10.0.0]# lltotal 48drwxr-xr-x. 3 root root  4096 May 17 21:32 bindrwxr-xr-x. 2 root root  4096 May 30 00:39 configdrwxr-xr-x. 2 root root  4096 May 30 00:36 libs-rw-r--r--. 1 root root 28824 May 17 21:26 LICENSE-rw-r--r--. 1 root root   336 May 17 21:26 NOTICEdrwxr-xr-x. 2 root root    46 May 17 21:32 site-docs[root@localhost kafka_2.11-0.10.0.0]# pwd/home/listen/kafka/kafka_2.11-0.10.0.0[root@localhost kafka_2.11-0.10.0.0]# mkdir logs[root@localhost kafka_2.11-0.10.0.0]# cd logs[root@localhost logs]# mkdir server0[root@localhost logs]# mkdir server1[root@localhost logs]# mkdir server2[root@localhost logs]# pwd/home/listen/kafka/kafka_2.11-0.10.0.0/logs[root@localhost logs]#

先启动Zookeeper集群

具体操作方法请查看

然后启动Kafka集群

[root@localhost kafka_2.11-0.10.0.0]# pwd/home/listen/kafka/kafka_2.11-0.10.0.0[root@localhost kafka_2.11-0.10.0.0]# bin/kafka-server-start.sh -daemon config/server.properties [root@localhost kafka_2.11-0.10.0.0]# pwd/home/listen/kafka/kafka_2.11-0.10.0.0[root@localhost kafka_2.11-0.10.0.0]# bin/kafka-server-start.sh -daemon config/server1.properties [root@localhost kafka_2.11-0.10.0.0]# pwd/home/listen/kafka/kafka_2.11-0.10.0.0[root@localhost kafka_2.11-0.10.0.0]# bin/kafka-server-start.sh -daemon config/server2.properties #以上是在后台启动，如果需要在console控制台启动看到运行信息，可参考下面的方式，这种方式需要开多窗口，否则无法启动第二个第三个节点[root@localhost kafka_2.11-0.10.0.0]# pwd/home/listen/kafka/kafka_2.11-0.10.0.0[root@localhost kafka_2.11-0.10.0.0]# bin/kafka-server-start.sh config/server.properties [root@localhost kafka_2.11-0.10.0.0]# pwd/home/listen/kafka/kafka_2.11-0.10.0.0[root@localhost kafka_2.11-0.10.0.0]# bin/kafka-server-start.sh config/server1.properties [root@localhost kafka_2.11-0.10.0.0]# pwd/home/listen/kafka/kafka_2.11-0.10.0.0[root@localhost kafka_2.11-0.10.0.0]# bin/kafka-server-start.sh config/server2.properties

启动成功，连接Zookeeper查看Kafka相关信息

[root@localhost zookeeper]# pwd/home/listen/zookeeper[root@localhost zookeeper]# zookeeper-2181/bin/zkCli.sh -server 192.168.75.141:2181[zk: 192.168.75.141:2181(CONNECTED) 0] ls /[dubbo, isr_change_notification, admin, zookeeper, consumers, config, controller, zk, brokers, controller_epoch][zk: 192.168.75.141:2181(CONNECTED) 1] ls /brokers[seqid, topics, ids][zk: 192.168.75.141:2181(CONNECTED) 2] ls /brokers/seqid[][zk: 192.168.75.141:2181(CONNECTED) 3] ls /brokers/topics[][zk: 192.168.75.141:2181(CONNECTED) 4] ls /brokers/ids   [2, 1, 0][zk: 192.168.75.141:2181(CONNECTED) 5]

Kafka常用命令操作

#手动创建topic，默认的topic只有一个分区，所以手动创建最佳[root@localhost ~]# cd /home/listen/kafka/kafka_2.11-0.10.0.0/#创建备份2个，分区2个，名称为meng的topic[root@localhost kafka_2.11-0.10.0.0]# bin/kafka-topics.sh --create --zookeeper 192.168.75.141:2181,192.168.75.141:2182,192.168.75.141:2183,192.168.75.141:2184,192.168.75.141:2185 --replication-factor 2 --partitions 2 --topic mengCreated topic "meng".[root@localhost kafka_2.11-0.10.0.0]##创建备份2个，分区8个，名称为t-meng的topic[root@localhost bin]# ./kafka-topics.sh --create --zookeeper 192.168.75.141:2181,192.168.75.141:2182,192.168.75.141:2183,192.168.75.141:2184,192.168.75.141:2185 --replication-factor 2 --partitions 8 --topic t-mengCreated topic "t-meng".[root@localhost bin]##将刚才的t-meng topic的分区修改为10个，即增加2个[root@localhost bin]# ./kafka-topics.sh --alter --zookeeper 192.168.75.141:2181,192.168.75.141:2182,192.168.75.141:2183,192.168.75.141:2184,192.168.75.141:2185 --partitions 10 --topic t-mengWARNING: If partitions are increased for a topic that has a key, the partition logic or ordering of the messages will be affectedAdding partitions succeeded![root@localhost bin]##减少分区，报错，分区只能增加不能减少[root@localhost bin]# ./kafka-topics.sh --alter --zookeeper 192.168.75.141:2181,192.168.75.141:2182,192.168.75.141:2183,192.168.75.141:2184,192.168.75.141:2185 --partitions 6 --topic t-mengWARNING: If partitions are increased for a topic that has a key, the partition logic or ordering of the messages will be affectedError while executing topic command : The number of partitions for a topic can only be increased[2016-06-02 00:58:31,143] ERROR kafka.admin.AdminOperationException: The number of partitions for a topic can only be increased	at kafka.admin.AdminUtils$.addPartitions(AdminUtils.scala:262)	at kafka.admin.TopicCommand$$anonfun$alterTopic$1.apply(TopicCommand.scala:148)	at kafka.admin.TopicCommand$$anonfun$alterTopic$1.apply(TopicCommand.scala:125)	at scala.collection.mutable.ResizableArray$class.foreach(ResizableArray.scala:59)	at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:48)	at kafka.admin.TopicCommand$.alterTopic(TopicCommand.scala:125)	at kafka.admin.TopicCommand$.main(TopicCommand.scala:63)	at kafka.admin.TopicCommand.main(TopicCommand.scala) (kafka.admin.TopicCommand$)[root@localhost bin]##查看分区信息[root@localhost kafka_2.11-0.10.0.0]# bin/kafka-topics.sh --describe --zookeeper 192.168.75.141:2181,192.168.75.141:2182,192.168.75.141:2183,192.168.75.141:2184,192.168.75.141:2185  --topic mengTopic:meng	PartitionCount:2	ReplicationFactor:2	Configs:	Topic: meng	Partition: 0	Leader: 1	Replicas: 1,2	Isr: 1,2	Topic: meng	Partition: 1	Leader: 2	Replicas: 2,0	Isr: 2,0[root@localhost kafka_2.11-0.10.0.0]##列出所有的topic[root@localhost bin]# ./kafka-topics.sh --zookeeper 192.168.75.141:2181,192.168.75.141:2182,192.168.75.141:2183,192.168.75.141:2184,192.168.75.141:2185 --list__consumer_offsetsbarfoomengmy-topicqiangt-zhout-zhou-2t-zhou-3testzhou[root@localhost bin]##删除一个topic，慎用[root@localhost bin]# ./kafka-topics.sh --delete --topic t-meng --zookeeper 192.168.75.141:2181,192.168.75.141:2182,192.168.75.141:2183,192.168.75.141:2184,192.168.75.141:2185Topic t-meng is marked for deletion.Note: This will have no impact if delete.topic.enable is not set to true.[root@localhost bin]# ./kafka-topics.sh --list --zookeeper 192.168.75.141:2181,192.168.75.141:2182,192.168.75.141:2183,192.168.75.141:2184,192.168.75.141:2185__consumer_offsetsbarfoomengmy-topicqiangt-meng - marked for deletiont-zhout-zhou-2t-zhou-3testzhou#marked for deletion标示为删除的标记，意思为逻辑删除，真正需要删除需要在server.properties文件中配置，标记为删除的topic其实还可以使用，没有任何的区别。#delete.topic.enable=true #是否真正的删除指定的topic，默认为false，可选配置#查看所有topic的分布描述[root@localhost bin]# ./kafka-topics.sh  --zookeeper 192.168.75.141:2181,192.168.75.141:2182,192.168.75.141:2183,192.168.75.141:2184,192.168.75.141:2185 --describeTopic:__consumer_offsets	PartitionCount:50	ReplicationFactor:3	Configs:segment.bytes=104857600,cleanup.policy=compact,compression.type=uncompressed	Topic: __consumer_offsets	Partition: 0	Leader: 1	Replicas: 1,2,0	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 1	Leader: 2	Replicas: 2,0,1	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 2	Leader: 0	Replicas: 0,1,2	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 3	Leader: 1	Replicas: 1,0,2	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 4	Leader: 2	Replicas: 2,1,0	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 5	Leader: 0	Replicas: 0,2,1	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 6	Leader: 1	Replicas: 1,2,0	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 7	Leader: 2	Replicas: 2,0,1	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 8	Leader: 0	Replicas: 0,1,2	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 9	Leader: 1	Replicas: 1,0,2	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 10	Leader: 2	Replicas: 2,1,0	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 11	Leader: 0	Replicas: 0,2,1	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 12	Leader: 1	Replicas: 1,2,0	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 13	Leader: 2	Replicas: 2,0,1	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 14	Leader: 0	Replicas: 0,1,2	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 15	Leader: 1	Replicas: 1,0,2	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 16	Leader: 2	Replicas: 2,1,0	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 17	Leader: 0	Replicas: 0,2,1	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 18	Leader: 1	Replicas: 1,2,0	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 19	Leader: 2	Replicas: 2,0,1	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 20	Leader: 0	Replicas: 0,1,2	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 21	Leader: 1	Replicas: 1,0,2	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 22	Leader: 2	Replicas: 2,1,0	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 23	Leader: 0	Replicas: 0,2,1	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 24	Leader: 1	Replicas: 1,2,0	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 25	Leader: 2	Replicas: 2,0,1	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 26	Leader: 0	Replicas: 0,1,2	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 27	Leader: 1	Replicas: 1,0,2	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 28	Leader: 2	Replicas: 2,1,0	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 29	Leader: 0	Replicas: 0,2,1	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 30	Leader: 1	Replicas: 1,2,0	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 31	Leader: 2	Replicas: 2,0,1	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 32	Leader: 0	Replicas: 0,1,2	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 33	Leader: 1	Replicas: 1,0,2	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 34	Leader: 2	Replicas: 2,1,0	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 35	Leader: 0	Replicas: 0,2,1	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 36	Leader: 1	Replicas: 1,2,0	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 37	Leader: 2	Replicas: 2,0,1	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 38	Leader: 0	Replicas: 0,1,2	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 39	Leader: 1	Replicas: 1,0,2	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 40	Leader: 2	Replicas: 2,1,0	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 41	Leader: 0	Replicas: 0,2,1	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 42	Leader: 1	Replicas: 1,2,0	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 43	Leader: 2	Replicas: 2,0,1	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 44	Leader: 0	Replicas: 0,1,2	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 45	Leader: 1	Replicas: 1,0,2	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 46	Leader: 2	Replicas: 2,1,0	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 47	Leader: 0	Replicas: 0,2,1	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 48	Leader: 1	Replicas: 1,2,0	Isr: 0,1,2	Topic: __consumer_offsets	Partition: 49	Leader: 2	Replicas: 2,0,1	Isr: 0,1,2Topic:bar	PartitionCount:1	ReplicationFactor:1	Configs:	Topic: bar	Partition: 0	Leader: 2	Replicas: 2	Isr: 2Topic:foo	PartitionCount:1	ReplicationFactor:1	Configs:	Topic: foo	Partition: 0	Leader: 1	Replicas: 1	Isr: 1Topic:meng	PartitionCount:2	ReplicationFactor:2	Configs:	Topic: meng	Partition: 0	Leader: 1	Replicas: 1,2	Isr: 1,2	Topic: meng	Partition: 1	Leader: 2	Replicas: 2,0	Isr: 0,2Topic:my-topic	PartitionCount:1	ReplicationFactor:1	Configs:	Topic: my-topic	Partition: 0	Leader: 0	Replicas: 0	Isr: 0Topic:qiang	PartitionCount:1	ReplicationFactor:1	Configs:	Topic: qiang	Partition: 0	Leader: 0	Replicas: 0	Isr: 0Topic:t-meng	PartitionCount:10	ReplicationFactor:2	Configs:	Topic: t-meng	Partition: 0	Leader: 0	Replicas: 0,2	Isr: 0,2	Topic: t-meng	Partition: 1	Leader: 1	Replicas: 1,0	Isr: 1,0	Topic: t-meng	Partition: 2	Leader: 2	Replicas: 2,1	Isr: 2,1	Topic: t-meng	Partition: 3	Leader: 0	Replicas: 0,1	Isr: 0,1	Topic: t-meng	Partition: 4	Leader: 1	Replicas: 1,2	Isr: 1,2	Topic: t-meng	Partition: 5	Leader: 2	Replicas: 2,0	Isr: 2,0	Topic: t-meng	Partition: 6	Leader: 0	Replicas: 0,2	Isr: 0,2	Topic: t-meng	Partition: 7	Leader: 1	Replicas: 1,0	Isr: 1,0	Topic: t-meng	Partition: 8	Leader: 2	Replicas: 2,0	Isr: 2,0	Topic: t-meng	Partition: 9	Leader: 0	Replicas: 0,2	Isr: 0,2Topic:t-zhou	PartitionCount:1	ReplicationFactor:1	Configs:	Topic: t-zhou	Partition: 0	Leader: 2	Replicas: 2	Isr: 2Topic:t-zhou-2	PartitionCount:1	ReplicationFactor:1	Configs:	Topic: t-zhou-2	Partition: 0	Leader: 0	Replicas: 0	Isr: 0Topic:t-zhou-3	PartitionCount:1	ReplicationFactor:1	Configs:	Topic: t-zhou-3	Partition: 0	Leader: 0	Replicas: 0	Isr: 0Topic:test	PartitionCount:1	ReplicationFactor:1	Configs:	Topic: test	Partition: 0	Leader: 1	Replicas: 1	Isr: 1Topic:zhou	PartitionCount:1	ReplicationFactor:1	Configs:	Topic: zhou	Partition: 0	Leader: 0	Replicas: 0	Isr: 0[root@localhost bin]##查看指定的topic信息[root@localhost bin]# ./kafka-topics.sh  --zookeeper 192.168.75.141:2181,192.168.75.141:2182,192.168.75.141:2183,192.168.75.141:2184,192.168.75.141:2185 --describe --topic t-mengTopic:t-meng	PartitionCount:10	ReplicationFactor:2	Configs:	Topic: t-meng	Partition: 0	Leader: 0	Replicas: 0,2	Isr: 0,2	Topic: t-meng	Partition: 1	Leader: 1	Replicas: 1,0	Isr: 1,0	Topic: t-meng	Partition: 2	Leader: 2	Replicas: 2,1	Isr: 2,1	Topic: t-meng	Partition: 3	Leader: 0	Replicas: 0,1	Isr: 0,1	Topic: t-meng	Partition: 4	Leader: 1	Replicas: 1,2	Isr: 1,2	Topic: t-meng	Partition: 5	Leader: 2	Replicas: 2,0	Isr: 2,0	Topic: t-meng	Partition: 6	Leader: 0	Replicas: 0,2	Isr: 0,2	Topic: t-meng	Partition: 7	Leader: 1	Replicas: 1,0	Isr: 1,0	Topic: t-meng	Partition: 8	Leader: 2	Replicas: 2,0	Isr: 2,0	Topic: t-meng	Partition: 9	Leader: 0	Replicas: 0,2	Isr: 0,2[root@localhost bin]#