正文

flume与kafka整合案例详解(代码片段)

ZeroTeam_麒麟  ZeroTeam_麒麟  2023-01-20  694

关键词：

环境配置

名称	版本	下载地址
Centos 7.0	64x	百度
Zookeeper	3.4.5
Flume	1.6.0
Kafka	2.1.0

配置Flume

这里就不介绍了零基础出门右转看Flume的文章

flume笔记

直接贴配置文件

[root@zero239 kafka_2.10-0.10.1.1]# cat /opt/hadoop/apache-flume-1.6.0-bin/conf/kafka-conf.properties 
# The configuration file needs to define the sources,
# the channels and the sinks.
# Sources, channels and sinks are defined per agent,
# in this case called 'agent'

agent.sources = r1
agent.channels = c1
agent.sinks = s1

# For each one of the sources, the type is defined
#agent.sources.r1.type = spooldir
#agent.sources.r1.command = /opt/test/logs/data
#agent.sources.r1.fileHeader = true
#agent.sources.r1.channels = c1

agent.sources.r1.type = spooldir
agent.sources.r1.spoolDir = /opt/test/logs/data
agent.sources.r1.fileHeader = true

# Each sink's type must be defined

#agent.sinks.s1.type = logger

agent.sinks.s1.type = org.apache.flume.sink.kafka.KafkaSink
agent.sinks.s1.topic = logstest
agent.sinks.s1.brokerList = zero230:9092
agent.sinks.s1.requiredAcks = 1
agent.sinks.s1.batchSize = 2


# Each channel's type is defined.
agent.channels.c1.type = memory
agent.channels.c1.capacity = 100
agent.sources.r1.channels = c1
agent.sinks.s1.channel = c1

配置Kafka

# 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=2

# Switch to enable topic deletion or not, default value is false
#delete.topic.enable=true

############################# 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://your.host.name: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/hadoop/kafka_2.10-0.10.1.1/logs/tmp

# 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

# 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=zero230:2181,zero231:2181,zero239:2181

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

我已经配置了集群Zookeeper所以在这里我指定是我配置的Zookeeper地址如果你没有配置的话可以直接使用Kafka内置的Zokeeper

Zookeeper集群搭建配置

启动Kafka验证是否成功

启动Zookeeper 如果没有配置集群的这一步跳过
启动Kafka内置Zookeeper

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

3.启动Kafka

server1.properties 为刚刚自己编辑的名称
bin/kafka-server-start.sh config/server1.properties

4.创建一个名为logstest的topic

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

5.查看Topic是否创建成功

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

6.创建一个生产端(相当于是一个已经数据产生的用户吧)这样容易理解

bin/kafka-console-producer.sh --broker-list zero230:9092 --topic logstest

7.创建一个消费端(意思就是可以看到生产者意思就是生产出来的数据可以看到输出)

bin/kafka-console-consumer.sh --zookeeper zero230:2181 --topic logstest --from-beginning

启动验证Flume是否能与Kafka对接

[root@zero239 apache-flume-1.6.0-bin]# ./bin/flume-ng agent --conf conf -f ./conf/kafka-conf.properties -n agent -Dflume.root.logger=INFO,console

对接成功截图

各位同学可以看到在Flumesinks配置中我设置的是Kafka意思就是输出到Kafka中

agent.sinks.s1.type = org.apache.flume.sink.kafka.KafkaSink
agent.sinks.s1.topic = logstest 刚刚创建的Topic名称
agent.sinks.s1.brokerList = zero230:9092 创建生产的机

在这里Flume与Kafka已经整合完毕了。

下节剧透

JAVA实现Kafka读取

flume+kafka+storm+redis大数据在线实时分析(代码片段)

...示中也能很好地说明这一点），即需要做各个系统之前的整合，包括Flume与Kafka的整合，Kafka与Storm的整合。当然，各个环境是否使用集群，依个人的实际需要而定，在我们的环境中，Flum 查看详情

flume整合kafka(基于kerberos认证)——完成实时数据采集(代码片段)

如果现在要想将flume中的sink设置为kafka，因为在实际的开发中，可能会有若干个子系统或者若干个客户端进行flume日志采集，那么能够承受这种采集任务量的只有kafka来完成，可是需要注意一个问题，现在的kafka是采用了Kerberos认... 查看详情

springboot2整合kafka组件，应用案例和流程详解(代码片段)

本文源码：GitHub·点这里||GitEE·点这里一、搭建Kafka环境1、下载解压--下载wgethttp://mirror.bit.edu.cn/apache/kafka/2.2.0/kafka_2.11-2.2.0.tgz--解压tar-zxvfkafka_2.11-2.2.0.tgz--重命名mvkafka_2.11-2.2.0kafka2.112、启动Kafka服务kafka依赖ZooKeeper服务，需要本... 查看详情

sparkstreaming整合kafka(代码片段)

项目架构：日志数据---->flume----->kafka-------->sparkstreaming---------->mysql/redis/hbase前置条件：安装zookeeper安装flume安装kafakhadoop实现高可用(1)实现flume收集数据到kafka启动kafak：nohupkafka-server-start.sh/application/kafka_2.11-1.1.0/config/serve... 查看详情

flume整合数据到kafka，sparkstreaming消费数据，并存储到hbase和redis中(代码片段)

目录1、模拟数据生成2、flume采集数据 1、node01配置flume的conf文件 2、node02开发flume的配置文件3、node03开发flume的配置文件4、开发flume启动停止脚本 5、node01执行以下命令创建kafka的topic6、启动并查看kafka的数据3、SparkStreaming消费ka... 查看详情

kafka集成整合外部插件（springboot，flume，flink，spark）(代码片段)

一kafka集成springboot1.工程结构 2.pom文件<parent><groupId>org.springframework.boot</groupId><artifactId>spring-boot-starter-parent</artifactId><version>2.6.1</version> 查看详情

flume整合kafka完成实时数据采集(代码片段)

agent选择agent1 execsource+memorychannel+avrosinkagent2 avrosource+memorychannel 模拟实际工作中的场景，agent1为A机器，agent2为B机器。 avrosource:监听avro端口，并且接收来自外部avro信息，avrosink：一般用于跨节点传输，主要绑定数... 查看详情

flume整合kafka

背景：系统的数据量越来越大，日志不能再简单的文件的保存，如此日志将会越来越大，也不方便查找与分析，综合考虑下使用了flume来收集日志，收集日志后向kafka传递消息，下面给出具体的配置#Theconfigurationfileneedstodefinet... 查看详情

day548.kafka相关外部系统整合-kafka(代码片段)

Kafka相关外部系统整合一、集成FlumeFlume是一个在大数据开发中非常常用的组件。可以用于Kafka的生产者，也可以用于Flume的消费者。1、Flume生产者启动kafka集群zk.shstartkf.shstart启动kafka消费者bin/kafka-console-consumer.sh--bootstrap-serverh... 查看详情

sparkstreaming基于sparkstreaming&flume&kafka打造通用流处理平台(代码片段)

通用流处理平台整合日志输出到Flume1.pom.xml2.结合log4j产生日志3.编写Flume配置文件streaming.conf4.Flume启动5.配置log4j.properties6.启动IDEA程序，查看日志接收情况整合Flume到Kafka1.启动zookeeper2.启动kafka3.查看Kafka的topic列表4.创建一个新... 查看详情

flume整合数据到kafka，sparkstreaming消费数据，并存储到hbase和redis中(代码片段)

kafka整合springboot以及核心参数的使用(代码片段)

kafka基本使用以及设计原理一，springboot整合kafka以及参数详解二，kafka核心参数详解2.1，生产者核心参数详解2.2，生产者核心参数详解三，kafka设计原理详解3.1，kafka的核心总控制器controller3.2，Partition副... 查看详情

flume整合kafka

flume整合kafka：flume采集业务日志，发送到kafka 安装部署KafkaDownload1.0.0isthelatestrelease.Thecurrentstableversionis1.0.0.Youcanverifyyourdownloadbyfollowingthese procedures andusingthese KEYS.1.0 查看详情

flume与kafka结合上传文件到hdfs上(代码片段)

实现如图的的效果(详细步骤请参考官方文档(http://flume.apache.org/FlumeUserGuide.html),flume更新版本比较快)flume1.conf的配置文件内容a1.sources=r1a1.sinks=k1a1.channels=c1#具体定义sourcea1.sources.r1.type=spooldir#先创建此目录，保证里面空的a1.sour 查看详情

互联网大数据日志收集离线实时分析实战案例

本文通过这个项目可以学到那些东西:Flume配置与使用Kafka配置与使用Kafka与Flume整合KafkaJavaAPI调用Hadoop搭建配置Mapreduce离线分析/数据清洗Storm 实时分析Sqoop迁移数据Hbase配置与使用查看详情

flume原理分析与使用案例(代码片段)

1、flume的特点：　　flume是一个分布式、可靠、和高可用的海量日志采集、聚合和传输的系统。支持在日志系统中定制各类数据发送方，用于收集数据；同时，Flume提供对数据进行简单处理，并写到各种数据接受方(比如文本、HDFS... 查看详情

flume整合kafka

1，安装并成功能运行flume2，安装并成功能运行kafka3，安装并成功能运行zookeeper4，开始整合flume收集的数据，写入kafkaa,修改flume的配置文加：vim flume_kafka.confagent1.sources=r1agent1.sinks=k1agent1.channels=c1#Describe/configurethesourceagent1.so 查看详情

flume(代码片段)

...入门2.1Flume安装部署2.1.1安装地址2.1.2安装部署2.2Flume入门案例2.2.1监控端口数据官方案例2.2.2实时监控单个追加文件-exec2.2.3实时监控目录下多个新文件-spooldir2.2.4实时监控目录下的多个追加文件-taildir3Flume进阶3.1Flume事务3.2FlumeAgent... 查看详情