flume-kafka环境搭建-mac单机模式

本文内容：（1）mac系统搭建单机模式flume、kafka
（2）flume监听本机端口并实时输出数据至控制台
（3）flume监听端口，发送数据至kafka，kafka消费数据

mac系统
flume版本：1.6.0
kafka版本：2.12
zookeeper版本：3.4.8

由于kafka依赖于ZooKeeper，因为安装kafka之前，需安装ZooKeeper

Zookeeper安装

zookeeper下载链接：https://zookeeper.apache.org/releases.html#download

1、下载zookeeper并解压
2、进入ZooKeeper目录，如：/Users/xx/kafka/zookeeper-3.4.8
3、将“zoo_sample.cfg”重命名为“zoo.cfg”
4、修改zoo.cfg
修改其中的dataDir

# The number of milliseconds of each tick
tickTime=2000
# The number of ticks that the initial
# synchronization phase can take
initLimit=10
# The number of ticks that can pass between
# sending a request and getting an acknowledgement
syncLimit=5
# the directory where the snapshot is stored.
# do not use /tmp for storage, /tmp here is just
# example sakes.
dataDir=/Users/xx/kafka/zookeeper-3.4.8/Data#
# the port at which the clients will connect
clientPort=2181
# the maximum number of client connections.
# increase this if you need to handle more clients
#maxClientCnxns=60
#
# Be sure to read the maintenance section of the
# administrator guide before turning on autopurge.
#
# http://zookeeper.apache.org/doc/current/zookeeperAdmin.html#sc_maintenance
#
# The number of snapshots to retain in dataDir
#autopurge.snapRetainCount=3
# Purge task interval in hours
# Set to "0" to disable auto purge feature
#autopurge.purgeInterval=1

5、进入/Users/xx/kafka/zookeeper-3.4.8/bin文件夹，启动ZooKeeper

sh zkServer.sh start

\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;36m\]\w\[\033[00m\]\$sh zkServer.sh start
ZooKeeper JMX enabled by default
Using config: /Users/xieyi01/kafka/zookeeper-3.4.8/bin/../conf/zoo.cfg
-n Starting zookeeper ...
STARTED

查看ZooKeeper状态

\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;36m\]\w\[\033[00m\]\$sh zkServer.sh status
ZooKeeper JMX enabled by default
Using config: /Users/xieyi01/kafka/zookeeper-3.4.8/bin/../conf/zoo.cfg
Mode: standalone

停止ZooKeeper

\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;36m\]\w\[\033[00m\]\$sh zkServer.sh stop
ZooKeeper JMX enabled by default
Using config: /Users/xieyi01/kafka/zookeeper-3.4.8/bin/../conf/zoo.cfg
-n Stopping zookeeper ...
STOPPED

kafka安装

kafka下载链接：http://archive.apache.org/dist/kafka/1.1.0/
1、下载kafka并解压
2、进入kafka目录，如：/Users/xx/kafka/kafka_2.12
3、在kafka目录下创建logs文件夹

mkdir logs

4、进入conf文件夹修改配置文件

cd config
vim server.properties

修改:
log.dirs=/Users/xieyi01/kafka/kafka_2.12/logs
zookeeper.connect=localhost:2181

# 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 = listener_name://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://your.host.name:9092

# Maps listener names to security protocols, the default is for them to be the same. See the config documentation for more details
#listener.security.protocol.map=PLAINTEXT:PLAINTEXT,SSL:SSL,SASL_PLAINTEXT:SASL_PLAINTEXT,SASL_SSL:SASL_SSL

# The number of threads that the server uses for receiving requests from the network and sending responses to the network
num.network.threads=3

# The number of threads that the server uses for processing requests, which may include 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 separated list of directories under which to store log files
log.dirs=/Users/xieyi01/kafka/kafka_2.12/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

############################# Internal Topic Settings  #############################
# The replication factor for the group metadata internal topics "__consumer_offsets" and "__transaction_state"
# For anything other than development testing, a value greater than 1 is recommended for to ensure availability such as 3.
offsets.topic.replication.factor=1
transaction.state.log.replication.factor=1
transaction.state.log.min.isr=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 excessive 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 due to age
log.retention.hours=168

# A size-based retention policy for logs. Segments are pruned from the log unless the remaining
# segments drop below log.retention.bytes. Functions independently of log.retention.hours.
#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=localhost:2181

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


############################# Group Coordinator Settings #############################

# The following configuration specifies the time, in milliseconds, that the GroupCoordinator will delay the initial consumer rebalance.
# The rebalance will be further delayed by the value of group.initial.rebalance.delay.ms as new members join the group, up to a maximum of max.poll.interval.ms.
# The default value for this is 3 seconds.
# We override this to 0 here as it makes for a better out-of-the-box experience for development and testing.
# However, in production environments the default value of 3 seconds is more suitable as this will help to avoid unnecessary, and potentially expensive, rebalances during application startup.
group.initial.rebalance.delay.ms=0

测试kafka

1、启动ZooKeeper
进入/Users/xx/kafka/zookeeper-3.4.8/bin文件夹，启动ZooKeeper

sh zkServer.sh start

查看ZooKeeper状态

\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;36m\]\w\[\033[00m\]\$sh zkServer.sh status
ZooKeeper JMX enabled by default
Using config: /Users/xieyi01/kafka/zookeeper-3.4.8/bin/../conf/zoo.cfg
Mode: standalone

查看当前java进程，可以看到ZooKeeper进程：QuorumPeerMain

\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;36m\]\w\[\033[00m\]\$jps
17058 Jps
13932
17054 QuorumPeerMain

2、启动kafka
进入kafka目录

sh bin/kafka-server-start.sh config/server.properties

查看kafka是否启动成功

\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;36m\]\w\[\033[00m\]\$jps
17073 Kafka
13932
17325 Jps
17054 QuorumPeerMain

3、创建topic命令

bin/kafka-topics.sh --zookeeper localhost:2181 --create --replication-factor 1 --partitions 1 --topic test

4、查看topic

bin/kafka-topics.sh --zookeeper localhost:2181 --list

5、生产者生产消息（以”test“这个topic为例）

bin/kafka-console-producer.sh --broker-list localhost:9092 --topic test

\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;36m\]\w\[\033[00m\]\$bin/kafka-console-producer.sh --broker-list localhost:9092 --topic test
>aa
>bb
>cc
>dd
>ef
>rg
>

6、消费者消费消息

bin/kafka-console-consumer.sh --bootstrap-server localhost:9092 --topic test --from-beginning

\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;36m\]\w\[\033[00m\]\$bin/kafka-console-consumer.sh --bootstrap-server localhost:9092 --topic test --from-beginning
aa
bb
cc
dd
ef
rg

flume安装

1、下载链接：http://archive.apache.org/dist/flume/
2、解压文件，将文件家存放在任意一个位置（如：/Users/xx/apache-flume-1.6.0-bin）

flume案例

flume监听端口的数据，输出至控制台

flume监听本机44444端口，通过telnet工具向本机44444端口发送数据，flume将监听的数据实时显示在控制台
1、进入flume的conf文件夹

cd /Users/xx/apache-flume-1.6.0-bin/conf

2、新建socket-log.conf

# example.conf: A single-node Flume configuration

# Name the components on this agent
a2.sources = r2
a2.sinks = k2
a2.channels = c2

# Describe/configure the source
a2.sources.r2.type = netcat
a2.sources.r2.bind = localhost
a2.sources.r2.port = 44444

# Describe the sink
a2.sinks.k2.type = logger

# Use a channel which buffers events in memory
a2.channels.c2.type = memory
a2.channels.c2.capacity = 1000
a2.channels.c2.transactionCapacity = 100

# Bind the source and sink to the channel
a2.sources.r2.channels = c2
a2.sinks.k2.channel = c2

3、开启socket-log.conf
进入flume文件夹

bin/flume-ng agent --conf conf --conf-file conf/socket-log.conf --name a2 -Dflume.root.logger=INFO,console

参数说明：

​	--conf conf/  ：表示配置文件存储在conf/目录

​	--name a1	：表示给agent起名为a1

​	--conf-file job/flume-telnet.conf ：flume本次启动读取的配置文件是在job文件夹下的flume-telnet.conf文件。

​	-Dflume.root.logger==INFO,console ：-D表示flume运行时动态修改flume.root.logger参数属性值，并将控制台日志打印级别设置为INFO级别。日志级别包括:log、info、warn、error。

4、telnet向端口发送数据，flume监听端口，并将数据打印至控制台
telnet向44444端口发送数据

\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;36m\]\w\[\033[00m\]\$telnet localhost 44444
Trying ::1...
telnet: connect to address ::1: Connection refused
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
aa
OK
bb
OK
cd
OK

flume监听44444端口的界面

2021-01-07 11:32:53,401 (SinkRunner-PollingRunner-DefaultSinkProcessor) [INFO - org.apache.flume.sink.LoggerSink.process(LoggerSink.java:94)] Event: { headers:{} body: 61 61 0D                                        aa. }
2021-01-07 11:32:53,824 (SinkRunner-PollingRunner-DefaultSinkProcessor) [INFO - org.apache.flume.sink.LoggerSink.process(LoggerSink.java:94)] Event: { headers:{} body: 62 62 0D                                        bb. }
2021-01-07 11:32:55,053 (SinkRunner-PollingRunner-DefaultSinkProcessor) [INFO - org.apache.flume.sink.LoggerSink.process(LoggerSink.java:94)] Event: { headers:{} body: 63 64 0D                                        cd. }

flume监听端口的数据，输出至kafka，kafka进行消费

1、进入flume的conf文件夹

cd /Users/xx/apache-flume-1.6.0-bin/conf

2、新建socket-kafka.conf

# Name the components on this agent
# example.conf: A single-node Flume configuration
# example.conf: A single-node Flume configuration

 # Name the components on this agent
 a1.sources = r1
 a1.sinks = k1
 a1.channels = c1

 # Describe/configure the source
 a1.sources.r1.type = netcat
 a1.sources.r1.bind = localhost
 a1.sources.r1.port = 44444

 # Describe the sink
 a1.sinks.k1.type = org.apache.flume.sink.kafka.KafkaSink
 a1.sinks.k1.kafka.bootstrap.servers = localhost:9092
 a1.sinks.k1.kafka.topic = test


 # Use a channel which buffers events in memory
 a1.channels.c1.type = memory
 a1.channels.c1.capacity = 1000
 a1.channels.c1.transactionCapacity = 100

 # Bind the source and sink to the channel
 a1.sources.r1.channels = c1
 a1.sinks.k1.channel = c1

3、开启socket-kafka.conf
进入flume文件夹

bin/flume-ng agent --conf conf --conf-file conf/socket-kafka.conf --name a1 -Dflume.root.logger=INFO,console

4、telnet向端口发送数据，flume监听端口，并将数据打印至控制台
telnet向44444端口发送数据

\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;36m\]\w\[\033[00m\]\$telnet localhost 44444
Trying ::1...
telnet: connect to address ::1: Connection refused
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
aa
OK
cc
OK
ok
OK

5、kafka消费“test”这个topic

\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;36m\]\w\[\033[00m\]\$bin/kafka-console-consumer.sh --bootstrap-server localhost:9092 --topic test --from-beginning
aa
bb
cc
dd
ef
rg