1. 写在前面

flume-ng高可用长在大数据处理环节第一个出现，对于处理日志文件有很好的作用，本篇博客将详细介绍flume-ng的高可用负载均衡搭建

2. flume-ng高可用负载均衡描述

在一般情况下，Flume-ng高可用采用server和client模式，client主要负责数据源source及数据流向端的sink指向配置，server主要负责数据流向sink详细配置，client需要将server的信息统一管理，server和sink之间数据连接通过channels

3. 配置server，这里配置三个server

flume-server1.properties

#set Agent name

agent.sources = r1

agent.channels = c1

agent.sinks = k1

#set channel

agent.channels.c1.type = memory

agent.channels.c1.capacity = 1024000

agent.channels.c1.transactionCapacity = 10000

agent.channels.c1.byteCapacity=134217728

agent.channels.c1.byteCapacityBufferPercentage=80

# other node,nna to nns

agent.sources.r1.type = avro

agent.sources.r1.bind = ynjz003

agent.sources.r1.port = 52020

agent.sources.r1.interceptors = i1

agent.sources.r1.interceptors.i1.type = static

agent.sources.r1.interceptors.i1.key = Collector

agent.sources.r1.interceptors.i1.value = ynjz003

agent.sources.r1.channels = c1

#set sink to hdfs

agent.sinks.k1.channel = c1

agent.sinks.k1.type = org.apache.flume.sink.kafka.KafkaSink

agent.sinks.k1.brokerList = ynjz003:9092,ynjz004:9092,ynjz005:9092,ynjz006:9092,ynjz007:9092,ynjz008:9092,ynjz009:9092

agent.sinks.k1.topic = flume-kafka-meijs33

agent.sinks.k1.serializer.class = kafka.serializer.StringEncoder

flume-server2.properties

#set Agent name

agent.sources = r1

agent.channels = c1

agent.sinks = k1

#set channel

agent.channels.c1.type = memory

agent.channels.c1.capacity = 1024000

agent.channels.c1.transactionCapacity = 10000

agent.channels.c1.byteCapacity=134217728

agent.channels.c1.byteCapacityBufferPercentage=80

# other node,nna to nns

agent.sources.r1.type = avro

agent.sources.r1.bind = ynjz004

agent.sources.r1.port = 52020

agent.sources.r1.interceptors = i1

agent.sources.r1.interceptors.i1.type = static

agent.sources.r1.interceptors.i1.key = Collector

agent.sources.r1.interceptors.i1.value = ynjz004

agent.sources.r1.channels = c1

#set sink to hdfs

agent.sinks.k1.channel = c1

agent.sinks.k1.type = org.apache.flume.sink.kafka.KafkaSink

agent.sinks.k1.brokerList = ynjz003:9092,ynjz004:9092,ynjz005:9092,ynjz006:9092,ynjz007:9092,ynjz008:9092,ynjz009:9092

agent.sinks.k1.topic = flume-kafka-meijs33

agent.sinks.k1.serializer.class = kafka.serializer.StringEncoder

flume-server3.properties

#set Agent name

agent.sources = r1

agent.channels = c1

agent.sinks = k1

#set channel

agent.channels.c1.type = memory

agent.channels.c1.capacity = 1024000

agent.channels.c1.transactionCapacity = 10000

agent.channels.c1.byteCapacity=134217728

agent.channels.c1.byteCapacityBufferPercentage=80

# other node,nna to nns

agent.sources.r1.type = avro

agent.sources.r1.bind = ynjz005

agent.sources.r1.port = 52020

agent.sources.r1.interceptors = i1

agent.sources.r1.interceptors.i1.type = static

agent.sources.r1.interceptors.i1.key = Collector

agent.sources.r1.interceptors.i1.value = ynjz005

agent.sources.r1.channels = c1

#set sink to hdfs

agent.sinks.k1.channel = c1

agent.sinks.k1.type = org.apache.flume.sink.kafka.KafkaSink

agent.sinks.k1.brokerList = ynjz003:9092,ynjz004:9092,ynjz005:9092,ynjz006:9092,ynjz007:9092,ynjz008:9092,ynjz009:9092

agent.sinks.k1.topic = flume-kafka-meijs33

agent.sinks.k1.serializer.class = kafka.serializer.StringEncoder

可以看出多个server配置的规律

3. 配置client，这里也配置一个client示例

flume-client.properties

#agent1 name

agent.channels = c1

agent.sources = r1

agent.sinks = k1 k2 k3 k4 k5 k6 k7

#set gruop

agent.sinkgroups = g1

#set channel

agent.channels.c1.type = memory

agent.channels.c1.capacity = 102400

agent.channels.c1.transactionCapacity = 1000

agent.channels.c1.byteCapacity=134217728

agent.channels.c1.byteCapacityBufferPercentage=80

agent.sources.r1.type = com.cbo.flume.source.zip.SpoolDirectorySource

agent.sources.r1.channels = c1

agent.sources.r1.spoolDir = /data/ynjz/workspace/zip

agent.sources.r1.fileHeader = true

agent.sources.r1.channels = c1

agent.sources.r1.flumeBatchSize=1000

agent.sources.r1.useFlumeEventFormat=false

agent.sources.r1.restart=true

agent.sources.r1.batchSize=1000

agent.sources.r1.batchTimeout=3000

agent.sources.r1.channels=c1

# set sink1

agent.sinks.k1.channel = c1

agent.sinks.k1.type = avro

agent.sinks.k1.hostname = ynjz003

agent.sinks.k1.port = 52020

# set sink2

agent.sinks.k2.channel = c1

agent.sinks.k2.type = avro

agent.sinks.k2.hostname = ynjz004

agent.sinks.k2.port = 52020

# set sink3

agent.sinks.k3.channel = c1

agent.sinks.k3.type = avro

agent.sinks.k3.hostname = ynjz005

agent.sinks.k3.port = 52020

# set sink4

agent.sinks.k1.channel = c1

agent.sinks.k1.type = avro

agent.sinks.k1.hostname = ynjz006

agent.sinks.k1.port = 52020

# set sink5

agent.sinks.k2.channel = c1

agent.sinks.k2.type = avro

agent.sinks.k2.hostname = ynjz007

agent.sinks.k2.port = 52020

# set sink6

agent.sinks.k3.channel = c1

agent.sinks.k3.type = avro

agent.sinks.k3.hostname = ynjz008

agent.sinks.k3.port = 52020

# set sink7

agent.sinks.k3.channel = c1

agent.sinks.k3.type = avro

agent.sinks.k3.hostname = ynjz009

agent.sinks.k3.port = 52020

#set sink group

agent.sinkgroups.g1.sinks = k1 k2 k3 k4 k5 k6 k7

#set failover

agent.sinkgroups.g1.processor.type = failover

agent.sinkgroups.g1.processor.priority.k1 = 10

agent.sinkgroups.g1.processor.priority.k2 = 10

agent.sinkgroups.g1.processor.priority.k3 = 10

agent.sinkgroups.g1.processor.priority.k4 = 10

agent.sinkgroups.g1.processor.priority.k5 = 10

agent.sinkgroups.g1.processor.priority.k6 = 10

agent.sinkgroups.g1.processor.priority.k7 = 10

agent.sinkgroups.g1.processor.maxpenalty = 10000

这里需要注意sinkgroups配置，flume sinkgroups在常用的应用中有两种方式failover和load_balance,failover可以理解为容错机制，在上面的配置中sink只会往一个kafka写入数据，但一个kafka挂了，failover机制会立马选举一个出来，所以这里的容错机制很完善，但是应对大数据量会影响数据写入的能力，所以建议在大数据量的时候采用load_balance配置，下面时配置示例

 #agent1 name

agent.channels = c1

agent.sources = r1

agent.sinks = k1 k2 k3 k4 k5 k6 k7

#set gruop

agent.sinkgroups = g1

#set channel

agent.channels.c1.type = memory

agent.channels.c1.capacity = 102400

agent.channels.c1.transactionCapacity = 24000

agent.channels.c1.byteCapacity=134217728

agent.channels.c1.byteCapacityBufferPercentage=80

agent.sources.r1.type = com.cbo.flume.source.zip.SpoolDirectorySource

agent.sources.r1.channels = c1

agent.sources.r1.spoolDir = /data/4G

agent.sources.r1.includePattern = ([^ ]*\.zip$)

agent.sources.r1.fileHeader = true

agent.sources.r1.channels = c1

agent.sources.r1.flumeBatchSize=10000

agent.sources.r1.useFlumeEventFormat=false

agent.sources.r1.restart=true

agent.sources.r1.batchSize=10000

agent.sources.r1.batchTimeout=3000

agent.sources.r1.channels=c1

# set sink1

agent.sinks.k1.channel = c1

agent.sinks.k1.type = avro

agent.sinks.k1.hostname = ynjz003

agent.sinks.k1.port = 52020

# set sink2

agent.sinks.k2.channel = c1

agent.sinks.k2.type = avro

agent.sinks.k2.hostname = ynjz004

agent.sinks.k2.port = 52020

# set sink3

agent.sinks.k3.channel = c1

agent.sinks.k3.type = avro

agent.sinks.k3.hostname = ynjz005

agent.sinks.k3.port = 52020

# set sink4

agent.sinks.k4.channel = c1

agent.sinks.k4.type = avro

agent.sinks.k4.hostname = ynjz006

agent.sinks.k4.port = 52020

# set sink5

agent.sinks.k5.channel = c1

agent.sinks.k5.type = avro

agent.sinks.k5.hostname = ynjz007

agent.sinks.k5.port = 52020

# set sink6

agent.sinks.k6.channel = c1

agent.sinks.k6.type = avro

agent.sinks.k6.hostname = ynjz008

agent.sinks.k6.port = 52020

# set sink7

agent.sinks.k7.channel = c1

agent.sinks.k7.type = avro

agent.sinks.k7.hostname = ynjz009

agent.sinks.k7.port = 52020

#set sink group

agent.sinkgroups.g1.sinks = k1 k2 k3 k4 k5 k6 k7

#set load_balance

agent.sinkgroups.g1.processor.type=load_balance

agent.sinkgroups.g1.processor.backoff=true

agent.sinkgroups.g1.processor.selector=random

在实际应用中多个client基本上一直，只有监控文件目录的配置不同即可agent.sources.r1.spoolDir = /data/4G

4. 启动flume-ng高可用集群

首先启动每个server,每个server只是配置文件flume-server-data.properties不同:

./bin/flume-ng agent --name agent --conf conf --conf-file conf/flume-server-data.properties -Dflume.root.logger=INFO,console > /data/ynjz/workspace/flume-server-data.log 2>&1 &

启动每个client,,每个server只是配置文件flume-client-data.properties不同:

./bin/flume-ng agent --name agent --conf conf --conf-file conf/flume-client-data.properties -Dflume.root.logger=INFO,console > /data/ynjz/workspace/flume-client-data.log 2>&1 &

在平时应用中，可以随时停止client，但停止了server没起而启动client会导致报错

Flume-ng高可用集群负载安装与配置的更多相关文章

  1. Flume 学习笔记之 Flume NG高可用集群搭建

    Flume NG高可用集群搭建: 架构总图: 架构分配: 角色 Host 端口 agent1 hadoop3 52020 collector1 hadoop1 52020 collector2 had ...

  2. 大数据高可用集群环境安装与配置（09）——安装Spark高可用集群

    1. 获取spark下载链接 登录官网:http://spark.apache.org/downloads.html 选择要下载的版本 2. 执行命令下载并安装 cd /usr/local/src/ ...

  3. Flume NG高可用集群搭建详解

    .Flume NG简述 Flume NG是一个分布式,高可用,可靠的系统,它能将不同的海量数据收集,移动并存储到一个数据存储系统中.轻量,配置简单,适用于各种日志收集,并支持 Failover和负载均 ...

  4. 大数据高可用集群环境安装与配置（06）——安装Hadoop高可用集群

    下载Hadoop安装包 登录 https://mirrors.tuna.tsinghua.edu.cn/apache/hadoop/common/ 镜像站,找到我们要安装的版本,点击进去复制下载链接 ...

  5. 大数据高可用集群环境安装与配置（07）——安装HBase高可用集群

    1. 下载安装包 登录官网获取HBase安装包下载地址 https://hbase.apache.org/downloads.html 2. 执行命令下载并安装 cd /usr/local/src/ ...

  6. 大数据高可用集群环境安装与配置（03）——设置SSH免密登录

    Hadoop的NameNode需要启动集群中所有机器的Hadoop守护进程,这个过程需要通过SSH登录来实现 Hadoop并没有提供SSH输入密码登录的形式,因此,为了能够顺利登录每台机器,需要将所有 ...

  7. 大数据高可用集群环境安装与配置（08）——安装Ganglia监控集群

    1. 安装依赖包和软件 在所有服务器上输入命令进行安装操作 yum install epel-release -y yum install ganglia-web ganglia-gmetad gan ...

  8. 大数据高可用集群环境安装与配置（02）——配置ntp服务

    NTP服务概述 NTP服务器[Network Time Protocol(NTP)]是用来使计算机时间同步化的一种协议,它可以使计算机对其服务器或时钟源(如石英钟,GPS等等)做同步化,它可以提供高精 ...

  9. 大数据高可用集群环境安装与配置（10）——安装Kafka高可用集群

    1. 获取安装包下载链接 访问https://kafka.apache.org/downloads 找到kafka对应版本 需要与服务器安装的scala版本一致(运行spark-shell可以看到当前 ...

随机推荐

  1. 洛谷 P1903 [国家集训队]数颜色 / 维护队列

    墨墨购买了一套N支彩色画笔(其中有些颜色可能相同),摆成一排,你需要回答墨墨的提问.墨墨会向你发布如下指令: 1. \(Q\) \(L\) \(R\) 代表询问你从第L支画笔到第R支画笔中共有几种不同 ...

  2. php对某个页面设置基础认证登录设置

    记录下. 对某个页面设置认证 代码最开始添加: <?php $user = 'test'; $password = '111111'; // 通过HTTP认证进行验证 if (!isset($_ ...

  3. mysql的服务器构成

    什么是实例 这里的实例不是类产生的实例对象,而是Linux系统下的一种机制 1.MySQL的后台进程+线程+预分配的内存结构. 2.MySQL在启动的过程中会启动后台守护进程,并生成工作线程,预分配内 ...

  4. maven settings.xml--需要保存到用户/.m2文件夹下

    <?xml version="1.0" encoding="UTF-8"?> <!-- Licensed to the Apache Soft ...

  5. 在PHP中如何把数组写成配置文件

    1.配置文件 <?php return array ( 556770 => '65460d6684dcad3d0a92f1feb7fde199', 567701 => '9c2acd ...

  6. Istio

    什么是Istio Istio是Service Mesh(服务网格)的主流实现方案.该方案降低了与微服务架构相关的复杂性,并提供了负载均衡.服务发现.流量管理.断路器.监控.故障注入和智能路由等功能特性 ...

  7. 自定义shiro实现权限验证方法isAccessAllowed

    由于Shiro filterChainDefinitions中 roles默认是and, admin= user,roles[system,general] 比如:roles[system,gener ...

  8. 为程序启用 守护进程-- supervisior

    待补充... Add this to your /etc/supervisord.conf: [rpcinterface:supervisor] supervisor.rpcinterface_fac ...

  9. kubernetes包管理工具Helm安装

    helm官方建议使用tls,首先生成证书. openssl genrsa -out ca.key.pem openssl req -key ca.key.pem -new -x509 -days -s ...

  10. elasticsearch 6.2.4添加用户密码认证

    elasticsearch 6.3版本之前的添加认证需安装x-pack插件,6.3之后貌似去掉了这个. 1.安装x-pack 先切换到elastic用户下,在执行以下命令 $cd /data/elas ...