./kafka-console-consumer.sh --zookeeper 192.168.86.133:2181,192.168.86.132:2181,192.168.86.134:2181 --topic shuaige --from-beginning
./kafka-console-producer.sh --broker-list 192.168.86.133:9092,192.168.86.132:9092,192.168.86.134:9092 --topic shuaige
./kafka-topics.sh --create --zookeeper 192.168.86.133:2181,192.168.86.132:2181,192.168.86.134:2181 --replication-factor 1 --partitions 1 --topic shuaigeck
2、几个错误
A [2017-06-23 12:31:29,338] WARN Bootstrap broker 192.168.86.133:9092 disconnected (org.apache.kafka.clients.NetworkClient)
原因不知
B kafka.common.KafkaException: Failed to acquire lock on file .lock in /opt/kafka/kafka-logs. A Kafka instance in another process or thread is using this directory.
没有创建log文件夹
C ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0
/opt/kafka/bin/kafka-server-start.sh /opt/kafka/config/server.properties & &命令必须
3、几个结果
[root@slave2 kafka-logs]# ll
总用量 12
-rw-r--r--. 1 root root 0 6月 23 12:10 cleaner-offset-checkpoint
-rw-r--r--. 1 root root 54 6月 23 12:10 meta.properties
-rw-r--r--. 1 root root 29 6月 23 12:49 recovery-point-offset-checkpoint
-rw-r--r--. 1 root root 29 6月 23 12:50 replication-offset-checkpoint
drwxr-xr-x. 2 root root 72 6月 23 12:48 shuaigeck-0[root@slave2 shuaigeck-0]# ll
总用量 4
-rw-r--r--. 1 root root 10485760 6月 23 12:48 00000000000000000000.index
-rw-r--r--. 1 root root 92 6月 23 12:50 00000000000000000000.log
查看下：
日志：
[root@slave2 shuaigeck-0]# ../../bin/kafka-run-class.sh kafka.tools.DumpLogSegments --files 00000000000000000000.log --print-data-log
Dumping 00000000000000000000.log
Starting offset: 0
offset: 0 position: 0 isvalid: true payloadsize: 7 magic: 1 compresscodec: NoCompressionCodec crc: 3388553551 payload: walasla
offset: 1 position: 41 isvalid: true payloadsize: 17 magic: 1 compresscodec: NoCompressionCodec crc: 879170540 payload: ssssssssssssssssss[root@slave2 shuaigeck-0]# ../../bin/kafka-run-class.sh kafka.tools.DumpLogSegments --files 00000000000000000000.index --print-data-log
Dumping 00000000000000000000.index
offset: 0 position: 0
几个配置
service.properties:
# The id of the broker. This must be set to a unique integer for each broker.
broker.id=0
host.name=192.168.86.133
############################# 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:9092
listeners=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://192.168.86.133:9092# The number of threads handling network requests
num.network.threads=3# The number of threads doing disk I/O
num.io.threads=8# The send buffer (SO_SNDBUF) used by the socket server
socket.send.buffer.bytes=102400# The receive buffer (SO_RCVBUF) used by the socket server
socket.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 files
log.dirs=/opt/kafka/kafka-logs# 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
message.max.byte=5242880
default.replication.factor=2
replica.fetch.max.bytes=5242880
############################# 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 deletion
log.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 policies
log.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.86.132:2181,192.168.86.133:2181,192.168.86.134:2181# Timeout in ms for connecting to zookeeper
zookeeper.connection.timeout.ms=6000
一个问题：
为什么所有的topic都不在我建立topic的机器上，这些topic都出现在其他节点？
命令)
