Flume profile case

defines the agent name as a1

source name is r1, if there are more than one, use space spacing

sink name is k1, channel name is c1

a1.sources = r1
a1.sinks = k1
a1.channels = c1
#组名名.属性名=属性值
a1.sources.r1.type=netcat
a1.sources.r1.bind=hadoop102
a1.sources.r1.port=99999

#定义sink
a1.sinks.k1.type=logger

#定义chanel
a1.channels.c1.type=memory
a1.channels.c1.capacity=1000

#连接组件 同一个source可以对接多个channel，一个sink只能从一个channel拿数据！
a1.sources.r1.channels=c1
a1.sinks.k1.channel=c1
		

Read More:

• Start flume agent and the solution of “a fatal error occurred while running” appears
• Node start – create a server listening port.
• Flume monitors a single append file in real time
• Port 4200 is already in use.Use ‘-port’ to specify a different port error Reasons
• Kafka opens JMX port and reports that the error port is occupied
• Through PID (process identification) to find the port (port) occupied applications, to solve the problem of port occupied
• View port and resolve port conflict in Windows
• source, ~/.bashrc, ~/.bash_ Profile details
• The Tomcat connector configured to listen on port 8080 failed to start. The port may already be in u
• Flume receives an error when a single message is too large
• Error found when loading /etc/profile when ubuntu18.04 is booted
• How to Fix Error accessing PRODUCT_USER_PROFILE
• iOS Xcode：Failed to create provisioning profile.
• Error:Failed to create provisioning profile. – iOS
• Centos Failed to Modify the port of SSH: error: Bind to port 27615 on 0.0.0.0 failed: Permission denied.
• File C:\Users\admin\Documents\WindowsPowerShell\profile.ps1 cannot be loaded because running scripts
• Implementation of Python switch / case statements
• Creating Server TCP listening socket 127.0.0.1:6379: bind: No error
• Python switch / case statement implementation method
• Creating Server TCP listening socket 127.0.0.1:6379: bind: No error。。。 Solutions to problems encountered in startup