kafka环境搭建

已经搭建好的zookeeper集群

下载kafka_2.11-0.10.0.1.tgz

tar -zxvf kafka_2.11-0.10.0.1.tgz

mv kafka_2.11-0.10.0.1 kafka

进入目录

cd kafka/config

修改配置文件

vim server.properties

broker.id=1
listeners=PLAINTEXT://:9092
num.network.threads=3
num.io.threads=8
socket.send.buffer.bytes=102400
socket.receive.buffer.bytes=102400
socket.request.max.bytes=104857600


############################# Log Basics #############################

# A comma seperated list of directories under which to store log files

#设置日志目录

log.dirs=/home/spark/opt/kafka/kafkalogs

# 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 deletion
log.retention.hours=168
message.max.byte=5242880
default.replication.factor=2
replica.fetch.max.bytes=5242880
# 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的连接端口

zookeeper.connect=master:2181,slave4:2181,slave5:2181

# Timeout in ms for connecting to zookeeper
zookeeper.connection.timeout.ms=6000

修改完保存

用scp -r发送到另外两台节点上

创建Topic来验证是否创建成功
创建Topic

./kafka-topics.sh --create --zookeeper master:2181 --replication-factor 2 --partitions 1 --topic my-topic

解释
    --replication-factor 2   #复制两份
    --partitions 1 #创建1个分区
    --topic #主题为my-topic
    -- ip??
在一台服务器上创建一个发布者
    创建一个broker，发布者(ip??,端口？？）
    ./kafka-console-producer.sh --broker-list slave4:9092 --topic my-topic
    此时：console处于阻塞状态，可以直接输入数据。
在一台服务器上创建一个订阅者
    ./kafka-console-consumer.sh --zookeeper slave5:12181 --topic my-topic --from-beginning
    此时：一旦有数据生成，此处的console中会显示数据