博客
关于我
No configuration found for this host:tier1
阅读量:125 次
发布时间:2019-02-26

本文共 2571 字,大约阅读时间需要 8 分钟。

flume启动时,如果没有通过参数(--name 或者 - n)指定代理,那么默认使用tier1作为代理名称,启动成功后,不会报错,但是可能会提示如题警告。

flume.conf配置文件默认就是用tier1作为代理名称。如下所示。

这个实例是网上一个正好使用了默认tier1作为agent,但是启动时却使用了"agent"作为agent,有点多余。再联系本文,不难推测这里启动时应该指定-n tier1。

指定正确的agent之后,启动会出现如下所示的日志。

2018-02-22 15:37:03,557 INFO org.apache.flume.node.PollingPropertiesFileConfigurationProvider: Configuration provider starting2018-02-22 15:37:03,582 INFO org.apache.flume.node.PollingPropertiesFileConfigurationProvider: Reloading configuration file:/opt/cm-5.12.0/run/cloudera-scm-agent/process/196-flume-AGENT/flume.conf2018-02-22 15:37:03,587 INFO org.apache.flume.conf.FlumeConfiguration: Processing:hdfs-sink-12018-02-22 15:37:03,587 INFO org.apache.flume.conf.FlumeConfiguration: Processing:hdfs-sink-12018-02-22 15:37:03,587 INFO org.apache.flume.conf.FlumeConfiguration: Processing:hdfs-sink-12018-02-22 15:37:03,587 INFO org.apache.flume.conf.FlumeConfiguration: Processing:hdfs-sink-12018-02-22 15:37:03,587 INFO org.apache.flume.conf.FlumeConfiguration: Added sinks: hdfs-sink-1 Agent: agent12018-02-22 15:37:03,588 INFO org.apache.flume.conf.FlumeConfiguration: Processing:hdfs-sink-12018-02-22 15:37:03,588 INFO org.apache.flume.conf.FlumeConfiguration: Processing:hdfs-sink-12018-02-22 15:37:03,588 INFO org.apache.flume.conf.FlumeConfiguration: Processing:hdfs-sink-12018-02-22 15:37:03,588 INFO org.apache.flume.conf.FlumeConfiguration: Processing:hdfs-sink-12018-02-22 15:37:03,588 INFO org.apache.flume.conf.FlumeConfiguration: Processing:hdfs-sink-12018-02-22 15:37:03,588 INFO org.apache.flume.conf.FlumeConfiguration: Processing:hdfs-sink-12018-02-22 15:37:03,588 INFO org.apache.flume.conf.FlumeConfiguration: Processing:hdfs-sink-12018-02-22 15:37:03,588 INFO org.apache.flume.conf.FlumeConfiguration: Processing:hdfs-sink-12018-02-22 15:37:03,588 INFO org.apache.flume.conf.FlumeConfiguration: Processing:hdfs-sink-12018-02-22 15:37:03,603 INFO org.apache.flume.conf.FlumeConfiguration: Post-validation flume configuration contains configuration for agents: [agent1]2018-02-22 15:37:03,603 INFO org.apache.flume.node.AbstractConfigurationProvider: Creating channels2018-02-22 15:37:03,654 INFO org.apache.flume.channel.DefaultChannelFactory: Creating instance of channel file-channel-1 type file2018-02-22 15:37:03,686 INFO org.apache.flume.node.AbstractConfigurationProvider: Created channel file-channel-12018-02-22 15:37:03,687 INFO org.apache.flume.source.DefaultSourceFactory: Creating instance of source kafka-source-1, type org.apache.flume.source.kafka.KafkaSource

如果是通过clouder-manager部署的flume,可以直接在实例配置界面做配置。

你可能感兴趣的文章
MySQL锁与脏读、不可重复读、幻读详解
查看>>
mysql锁机制,主从复制
查看>>
Mysql锁机制,行锁表锁
查看>>
MySQL集群解决方案(4):负载均衡
查看>>
mysql面试题学校三表查询_mysql三表查询分组后取每组最大值,mysql面试题。
查看>>
Mysql面试题精选
查看>>
MySQL面试题集锦
查看>>
mysql颠覆实战笔记(八)--mysql的自定义异常处理怎么破
查看>>
mysql驱动、durid、mybatis之间的关系
查看>>
mysql驱动支持中文_mysql 驱动包-Go语言中文社区
查看>>
MySQL高可用切换_(5.9)mysql高可用系列——正常主从切换测试
查看>>
MySQL高可用解决方案详解
查看>>
MYSQL高可用集群MHA架构
查看>>
MySQL高级-MySQL并发参数调整
查看>>
MySQL高级-MySQL查询缓存优化
查看>>
MySQL高级-MySQL锁
查看>>
MySQL高级-SQL优化步骤
查看>>
MySQL高级-内存管理及优化
查看>>
MySQL高级-视图
查看>>
MySQL高级-触发器
查看>>