Kafka命令行操作案例
Kafka命令行操作案例
作者：尹正杰
版权声明：原创作品，谢绝转载！否则将追究法律责任。
一.管理topic脚本(kafka-topics.sh)
1>.查看脚本的帮助信息
[root@kafka201.yinzhengjie.com ~]# kafka-topics.sh --help This tool helps to create, delete, describe, or change a topic. Option Description ------ ----------- --alter Alter the number of partitions, replica assignment, and/or configuration for the topic. --at-min-isr-partitions if set when describing topics, only show partitions whose isr count is equal to the configured minimum. Not supported with the --zookeeper option. --bootstrap-server <String: server to REQUIRED: The Kafka server to connect connect to> to. In case of providing this, a direct Zookeeper connection won't be required. --command-config <String: command Property file containing configs to be config property file> passed to Admin Client. This is used only with --bootstrap-server option for describing and altering broker configs. --config <String: name=value> A topic configuration override for the topic being created or altered.The following is a list of valid configurations: cleanup.policy compression.type delete.retention.ms file.delete.delay.ms flush.messages flush.ms follower.replication.throttled. replicas index.interval.bytes leader.replication.throttled.replicas max.compaction.lag.ms max.message.bytes message.downconversion.enable message.format.version message.timestamp.difference.max.ms message.timestamp.type min.cleanable.dirty.ratio min.compaction.lag.ms min.insync.replicas preallocate retention.bytes retention.ms segment.bytes segment.index.bytes segment.jitter.ms segment.ms unclean.leader.election.enable See the Kafka documentation for full details on the topic configs.It is supported only in combination with -- create if --bootstrap-server option is used. --create Create a new topic. --delete Delete a topic --delete-config <String: name> A topic configuration override to be removed for an existing topic (see the list of configurations under the --config option). Not supported with the --bootstrap-server option. --describe List details for the given topics. --disable-rack-aware Disable rack aware replica assignment --exclude-internal exclude internal topics when running list or describe command. The internal topics will be listed by default --force Suppress console prompts --help Print usage information. --if-exists if set when altering or deleting or describing topics, the action will only execute if the topic exists. Not supported with the --bootstrap- server option. --if-not-exists if set when creating topics, the action will only execute if the topic does not already exist. Not supported with the --bootstrap- server option. --list List all available topics. --partitions <Integer: # of partitions> The number of partitions for the topic being created or altered (WARNING: If partitions are increased for a topic that has a key, the partition logic or ordering of the messages will be affected). If not supplied for create, defaults to the cluster default. --replica-assignment <String: A list of manual partition-to-broker broker_id_for_part1_replica1 : assignments for the topic being broker_id_for_part1_replica2 , created or altered. broker_id_for_part2_replica1 : broker_id_for_part2_replica2 , ...> --replication-factor <Integer: The replication factor for each replication factor> partition in the topic being created. If not supplied, defaults to the cluster default. --topic <String: topic> The topic to create, alter, describe or delete. It also accepts a regular expression, except for --create option. Put topic name in double quotes and use the '\' prefix to escape regular expression symbols; e. g. "test\.topic". --topics-with-overrides if set when describing topics, only show topics that have overridden configs --unavailable-partitions if set when describing topics, only show partitions whose leader is not available --under-min-isr-partitions if set when describing topics, only show partitions whose isr count is less than the configured minimum. Not supported with the --zookeeper option. --under-replicated-partitions if set when describing topics, only show under replicated partitions --version Display Kafka version. --zookeeper <String: hosts> DEPRECATED, The connection string for the zookeeper connection in the form host:port. Multiple hosts can be given to allow fail-over. [root@kafka201.yinzhengjie.com ~]#
2>.创建topic
[root@kafka201.yinzhengjie.com ~]# kafka-topics.sh --zookeeper 172.200.4.202:2181/yinzhengjie-kafka --create --topic yinzhengjie-kafka --partitions 3 --replication-factor 2 Created topic yinzhengjie-kafka. [root@kafka201.yinzhengjie.com ~]#
[root@kafka201.yinzhengjie.com ~]# kafka-topics.sh --bootstrap-server 172.200.4.202:9092 --create --partitions 3 --replication-factor 2 --topic filebeat-ubuntu-syslog Created topic filebeat-ubuntu-syslog. [root@kafka201.yinzhengjie.com ~]#
3>.查看已存在的topic列表
[root@kafka201.yinzhengjie.com ~]# kafka-topics.sh --zookeeper 172.200.4.202:2181/yinzhengjie-kafka --list yinzhengjie-kafka [root@kafka201.yinzhengjie.com ~]#
[root@kafka201.yinzhengjie.com ~]# kafka-topics.sh --bootstrap-server 172.200.4.202:9092 --list yinzhengjie-kafka [root@kafka201.yinzhengjie.com ~]#
4>.列出给定主题的详细信息
[root@kafka201.yinzhengjie.com ~]# kafka-topics.sh --zookeeper 172.200.4.202:2181/yinzhengjie-kafka --describe Topic: yinzhengjie-kafka PartitionCount: 3 ReplicationFactor: 2 Configs: Topic: yinzhengjie-kafka Partition: 0 Leader: 201 Replicas: 201,202 Isr: 201,202 Topic: yinzhengjie-kafka Partition: 1 Leader: 202 Replicas: 202,203 Isr: 202,203 Topic: yinzhengjie-kafka Partition: 2 Leader: 203 Replicas: 203,201 Isr: 203,201 [root@kafka201.yinzhengjie.com ~]#
[root@kafka201.yinzhengjie.com ~]# kafka-topics.sh --bootstrap-server 172.200.4.202:9092 --describe Topic: yinzhengjie-kafka PartitionCount: 3 ReplicationFactor: 2 Configs: segment.bytes=536870912,max.message.bytes=104857600 Topic: yinzhengjie-kafka Partition: 0 Leader: 201 Replicas: 201,202 Isr: 201,202 Topic: yinzhengjie-kafka Partition: 1 Leader: 202 Replicas: 202,203 Isr: 202,203 Topic: yinzhengjie-kafka Partition: 2 Leader: 203 Replicas: 203,201 Isr: 203,201 [root@kafka201.yinzhengjie.com ~]#
5>.删除topic
[root@kafka201.yinzhengjie.com ~]# kafka-topics.sh --zookeeper 172.200.4.202:2181/yinzhengjie-kafka --list yinzhengjie-kafka [root@kafka201.yinzhengjie.com ~]# [root@kafka201.yinzhengjie.com ~]# kafka-topics.sh --zookeeper 172.200.4.202:2181/yinzhengjie-kafka --delete --topic yinzhengjie-kafka Topic yinzhengjie-kafka is marked for deletion. Note: This will have no impact if delete.topic.enable is not set to true. [root@kafka201.yinzhengjie.com ~]# [root@kafka201.yinzhengjie.com ~]# kafka-topics.sh --zookeeper 172.200.4.202:2181/yinzhengjie-kafka --list [root@kafka201.yinzhengjie.com ~]# [root@kafka201.yinzhengjie.com ~]#
[root@kafka201.yinzhengjie.com ~]# kafka-topics.sh --bootstrap-server 172.200.4.202:9092 --list yinzhengjie-kafka [root@kafka201.yinzhengjie.com ~]# [root@kafka201.yinzhengjie.com ~]# kafka-topics.sh --bootstrap-server 172.200.4.202:9092 --delete --topic yinzhengjie-kafka [root@kafka201.yinzhengjie.com ~]# [root@kafka201.yinzhengjie.com ~]# kafka-topics.sh --bootstrap-server 172.200.4.202:9092 --list [root@kafka201.yinzhengjie.com ~]# [root@kafka201.yinzhengjie.com ~]#
6>.修改kakfa的分区数
温馨提示:
当我们把kafka的某个topic的分区数进行扩容操作后，后续写入的数据会均衡到其它的partition中。
为什么kafka的分区数只能增加却不能减少呢？
一个正在运行的kafka集群，每个partition都是有数据存储的，如果想要减少分区数，首先需要先将某些partition的数据移动到其它partition中，然后再执行删除操作。但这无疑是代码里庞大的工程，因此官方暂时未支持减少分区数的功能。
[root@kafka201.yinzhengjie.com ~]# kafka-topics.sh --bootstrap-server 172.200.4.202:9092 --list yinzhengjie-kafka [root@kafka201.yinzhengjie.com ~]# [root@kafka201.yinzhengjie.com ~]# kafka-topics.sh --bootstrap-server 172.200.4.202:9092 --describe Topic: yinzhengjie-kafka PartitionCount: 3 ReplicationFactor: 2 Configs: segment.bytes=536870912,max.message.bytes=104857600 Topic: yinzhengjie-kafka Partition: 0 Leader: 202 Replicas: 202,201 Isr: 202,201 Topic: yinzhengjie-kafka Partition: 1 Leader: 203 Replicas: 203,202 Isr: 203,202 Topic: yinzhengjie-kafka Partition: 2 Leader: 201 Replicas: 201,203 Isr: 201,203 [root@kafka201.yinzhengjie.com ~]# [root@kafka201.yinzhengjie.com ~]# kafka-topics.sh --bootstrap-server 172.200.4.202:9092 --alter --topic yinzhengjie-kafka --partitions 20 [root@kafka201.yinzhengjie.com ~]# [root@kafka201.yinzhengjie.com ~]# kafka-topics.sh --bootstrap-server 172.200.4.202:9092 --describe Topic: yinzhengjie-kafka PartitionCount: 20 ReplicationFactor: 2 Configs: segment.bytes=536870912,max.message.bytes=104857600 Topic: yinzhengjie-kafka Partition: 0 Leader: 202 Replicas: 202,201 Isr: 202,201 Topic: yinzhengjie-kafka Partition: 1 Leader: 203 Replicas: 203,202 Isr: 203,202 Topic: yinzhengjie-kafka Partition: 2 Leader: 201 Replicas: 201,203 Isr: 201,203 Topic: yinzhengjie-kafka Partition: 3 Leader: 202 Replicas: 202,203 Isr: 202,203 Topic: yinzhengjie-kafka Partition: 4 Leader: 203 Replicas: 203,201 Isr: 203,201 Topic: yinzhengjie-kafka Partition: 5 Leader: 201 Replicas: 201,202 Isr: 201,202 Topic: yinzhengjie-kafka Partition: 6 Leader: 202 Replicas: 202,201 Isr: 202,201 Topic: yinzhengjie-kafka Partition: 7 Leader: 203 Replicas: 203,202 Isr: 203,202 Topic: yinzhengjie-kafka Partition: 8 Leader: 201 Replicas: 201,203 Isr: 201,203 Topic: yinzhengjie-kafka Partition: 9 Leader: 202 Replicas: 202,203 Isr: 202,203 Topic: yinzhengjie-kafka Partition: 10 Leader: 203 Replicas: 203,201 Isr: 203,201 Topic: yinzhengjie-kafka Partition: 11 Leader: 201 Replicas: 201,202 Isr: 201,202 Topic: yinzhengjie-kafka Partition: 12 Leader: 202 Replicas: 202,201 Isr: 202,201 Topic: yinzhengjie-kafka Partition: 13 Leader: 203 Replicas: 203,202 Isr: 203,202 Topic: yinzhengjie-kafka Partition: 14 Leader: 201 Replicas: 201,203 Isr: 201,203 Topic: yinzhengjie-kafka Partition: 15 Leader: 202 Replicas: 202,203 Isr: 202,203 Topic: yinzhengjie-kafka Partition: 16 Leader: 203 Replicas: 203,201 Isr: 203,201 Topic: yinzhengjie-kafka Partition: 17 Leader: 201 Replicas: 201,202 Isr: 201,202 Topic: yinzhengjie-kafka Partition: 18 Leader: 202 Replicas: 202,201 Isr: 202,201 Topic: yinzhengjie-kafka Partition: 19 Leader: 203 Replicas: 203,202 Isr: 203,202 [root@kafka201.yinzhengjie.com ~]#
7>.
二.测试kafka集群的可用性
1>.创建生产者
[root@kafka201.yinzhengjie.com ~]# kafka-console-producer.sh --help This tool helps to read data from standard input and publish it to Kafka. Option Description ------ ----------- --batch-size <Integer: size> Number of messages to send in a single batch if they are not being sent synchronously. (default: 200) --bootstrap-server <String: server to REQUIRED unless --broker-list connect to> (deprecated) is specified. The server (s) to connect to. The broker list string in the form HOST1:PORT1,HOST2: PORT2. --broker-list <String: broker-list> DEPRECATED, use --bootstrap-server instead; ignored if --bootstrap- server is specified. The broker list string in the form HOST1:PORT1, HOST2:PORT2. --compression-codec [String: The compression codec: either 'none', compression-codec] 'gzip', 'snappy', 'lz4', or 'zstd'. If specified without value, then it defaults to 'gzip' --help Print usage information. --line-reader <String: reader_class> The class name of the class to use for reading lines from standard in. By default each line is read as a separate message. (default: kafka. tools. ConsoleProducer$LineMessageReader) --max-block-ms <Long: max block on The max time that the producer will send> block for during a send request (default: 60000) --max-memory-bytes <Long: total memory The total memory used by the producer in bytes> to buffer records waiting to be sent to the server. (default: 33554432) --max-partition-memory-bytes <Long: The buffer size allocated for a memory in bytes per partition> partition. When records are received which are smaller than this size the producer will attempt to optimistically group them together until this size is reached. (default: 16384) --message-send-max-retries <Integer> Brokers can fail receiving the message for multiple reasons, and being unavailable transiently is just one of them. This property specifies the number of retires before the producer give up and drop this message. (default: 3) --metadata-expiry-ms <Long: metadata The period of time in milliseconds expiration interval> after which we force a refresh of metadata even if we haven't seen any leadership changes. (default: 300000) --producer-property <String: A mechanism to pass user-defined producer_prop> properties in the form key=value to the producer. --producer.config <String: config file> Producer config properties file. Note that [producer-property] takes precedence over this config. --property <String: prop> A mechanism to pass user-defined properties in the form key=value to the message reader. This allows custom configuration for a user- defined message reader. Default properties include: parse.key=true|false key.separator=<key.separator> ignore.error=true|false --request-required-acks <String: The required acks of the producer request required acks> requests (default: 1) --request-timeout-ms <Integer: request The ack timeout of the producer timeout ms> requests. Value must be non-negative and non-zero (default: 1500) --retry-backoff-ms <Integer> Before each retry, the producer refreshes the metadata of relevant topics. Since leader election takes a bit of time, this property specifies the amount of time that the producer waits before refreshing the metadata. (default: 100) --socket-buffer-size <Integer: size> The size of the tcp RECV size. (default: 102400) --sync If set message send requests to the brokers are synchronously, one at a time as they arrive. --timeout <Integer: timeout_ms> If set and the producer is running in asynchronous mode, this gives the maximum amount of time a message will queue awaiting sufficient batch size. The value is given in ms. (default: 1000) --topic <String: topic> REQUIRED: The topic id to produce messages to. --version Display Kafka version. [root@kafka201.yinzhengjie.com ~]#
[root@kafka201.yinzhengjie.com ~]# kafka-console-producer.sh --broker-list 172.200.4.202:9092 --topic yinzhengjie-kafka >hello >world >
2>.创建消费者
[root@kafka201.yinzhengjie.com ~]# kafka-console-consumer.sh --help This tool helps to read data from Kafka topics and outputs it to standard output. Option Description ------ ----------- --bootstrap-server <String: server to REQUIRED: The server(s) to connect to. connect to> --consumer-property <String: A mechanism to pass user-defined consumer_prop> properties in the form key=value to the consumer. --consumer.config <String: config file> Consumer config properties file. Note that [consumer-property] takes precedence over this config. --enable-systest-events Log lifecycle events of the consumer in addition to logging consumed messages. (This is specific for system tests.) --formatter <String: class> The name of a class to use for formatting kafka messages for display. (default: kafka.tools. DefaultMessageFormatter) --from-beginning If the consumer does not already have an established offset to consume from, start with the earliest message present in the log rather than the latest message. --group <String: consumer group id> The consumer group id of the consumer. --help Print usage information. --isolation-level <String> Set to read_committed in order to filter out transactional messages which are not committed. Set to read_uncommitted to read all messages. (default: read_uncommitted) --key-deserializer <String: deserializer for key> --max-messages <Integer: num_messages> The maximum number of messages to consume before exiting. If not set, consumption is continual. --offset <String: consume offset> The offset id to consume from (a non- negative number), or 'earliest' which means from beginning, or 'latest' which means from end (default: latest) --partition <Integer: partition> The partition to consume from. Consumption starts from the end of the partition unless '--offset' is specified. --property <String: prop> The properties to initialize the message formatter. Default properties include: print.timestamp=true|false print.key=true|false print.value=true|false key.separator=<key.separator> line.separator=<line.separator> key.deserializer=<key.deserializer> value.deserializer=<value. deserializer> Users can also pass in customized properties for their formatter; more specifically, users can pass in properties keyed with 'key. deserializer.' and 'value. deserializer.' prefixes to configure their deserializers. --skip-message-on-error If there is an error when processing a message, skip it instead of halt. --timeout-ms <Integer: timeout_ms> If specified, exit if no message is available for consumption for the specified interval. --topic <String: topic> The topic id to consume on. --value-deserializer <String: deserializer for values> --version Display Kafka version. --whitelist <String: whitelist> Regular expression specifying whitelist of topics to include for consumption. [root@kafka201.yinzhengjie.com ~]#
[root@kafka201.yinzhengjie.com ~]# kafka-console-consumer.sh --bootstrap-server 172.200.4.202:9092 --topic yinzhengjie-kafka --from-beginning hello world
三.
当你的才华还撑不起你的野心的时候，你就应该静下心来学习。当你的能力还驾驭不了你的目标的时候，你就应该沉下心来历练。问问自己，想要怎样的人生。 欢迎加入基础架构自动化运维：598432640，大数据SRE进阶之路：959042252，DevOps进阶之路：526991186
