flume app

Flume ng High Availability Cluster Setup:Overall diagram of the architecture:Schema allocation: Role Host Port Agent1 Hadoop3 52020 Collector1 Hadoop1 52020 Collector2 Hadoop2 52020 Agent1 configuration (flume-client.conf):#agent1 nameagent1.channels = c1agent1.sources = R1agent1.sinks = K1 K2#set gruopa

I. Introduction of FlumeFlume is a distributed, reliable, and highly available mass-log aggregation system that enables the customization of various data senders in the system for data collection, while Flume provides the ability to simply process the data and write to various data-receiving parties (customizable).Design goal:(1) ReliabilityWhen a node fails, the log can be transmitted to other nodes without loss.

First, IntroductionRecently in the study of Big data analysis related work, for which the use of the collection part used to Flume, deliberately spent a little time to understand the flume work principle and working mechanism. A personal understanding of a new system first, after a rough understanding of its rationale, and then from the source code to understand some of its key implementation part, and fina

flume– primary knowledge of Flume, source and sinkDirectoryBasic conceptsCommon source sourcesCommon sinkBasic conceptsWhat's the name flume?Distributed, reliable, large number of log collection, aggregation, and mobility tools.? eventsevent, which is the byte data of a row of data, is the basic unit of Flume sending f

Recently learned the use of the next flume, in line with the company will be independent of the development of the log system, the official website user manual: Http://flume.apache.org/FlumeUserGuide.htmlFlume schema A. ComponentFirst move, the structure of the Internet.As you can see from the diagram, the Flume event is defined as a data stream, a data stream consisting of an agent, which is actually a JVM

= staticApp.sources.r1.interceptors.i3.key = Flume.client.system.flagApp.sources.r1.interceptors.i3.value = Client system marked #设置系统标示, such as S001App.channels.c1.type = Memoryapp.channels.c1.capacity = 1000app.channels.c1.transactionCapacity = 1000App.channels.c1.keep-alive = 3App.channels.c1.byteCapacityBufferPercentage = 30App.channels.c1.byteCapacity = 104857600App.sinks.k1.type = AvroApp.sinks.k1.hostname = 172.19.100.92App.sinks.k1.port = 44466App.sinks.k2.type = AvroApp.sinks.k2.hostn

I am testing HDFs sink, found that the sink side of the file scrolling configuration items do not play any role, configured as follows:a1.sinks.k1.type=hdfsa1.sinks.k1.channel=c1a1.sinks.k1.hdfs.uselocaltimestamp=truea1.sinks.k1.hdfs.path=hdfs:/ /192.168.11.177:9000/flume/events/%y/%m/%d/%h/%ma1.sinks.k1.hdfs.fileprefix=xxxa1.sinks.k1.hdfs.rollinterval= 60a1.sinks.k1.hdfs.rollsize=0a1.sinks.k1.hdfs.rollcount=0a1.sinks.k1.hdfs.idletimeout=0The configur

," + "increasing capacity, or increasing thread count") ; } Take before also pre-judgment, if the takelist is full, indicating take operation is too slow, there is an event accumulation phenomenon, you should adjust the transaction capacitywhat happens when a transaction commits, and what does the transaction commit?? Commit is a transaction commitTwo cases:1, put the event submissionwhile (!putlist.isempty ()) { if (!queue.offer (Putlist.removefirst ())) {