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
p>
div>
Read More:
- Start flume agent and the solution of “a fatal error occurred while running” appears
- Flume monitors a single append file in real time
- Memory configuration of BIOS combat
- Edge detection: two methods
- Conda HTTP 000 CONNECTION FAILED for url
- [latex] latex adjust row spacing
- Backup and recovery – rman4
- Centos7 view and close firewall
- Tensorflow installation and uninstall (Anaconda version)
- (Solved) pytorch error: RuntimeError: cuDNN error: CUDNN_STATUS_EXECUTION_FAILED (install cuda)
- Elasticsearch startup process error: org.elasticsearch.transport .BindTransportException: Failed to bind to [9300-9400
- nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
- Common problems of Hadoop startup error reporting
- ssh port forwarding
- Error: transport error 202: bind failed: address already in use
- Building virtual machine environment based on kvm-qemu under ubuntu12.10 (12)
- CONDA install torch error
- Attributeerror: ‘module’ object has no attribute ‘handlers’ — Python sub module import problem
- display:inline-block Solution to the gap problem
- hdfs 192.168.2.19:9000 failed on connection exception: java.net.ConnectException:Connection refused