博客
关于我
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里为什么会建议不要使用SELECT *?
查看>>
MySQL里的那些日志们
查看>>
MySQL锁
查看>>
MySQL锁与脏读、不可重复读、幻读详解
查看>>
MySQL锁机制
查看>>
mysql锁机制,主从复制
查看>>
Mysql锁机制,行锁表锁
查看>>
MySQL锁表问题排查
查看>>
Mysql锁(1):锁概述和全局锁的介绍
查看>>
Mysql锁(2):表级锁
查看>>
MySQL锁,锁的到底是什么?
查看>>
MySQL错误-this is incompatible with sql_mode=only_full_group_by完美解决方案
查看>>
Mysql错误2003 -Can't connect toMySQL server on 'localhost'(10061)解决办法
查看>>
MySQL错误提示mysql Statement violates GTID consistency
查看>>
mysql错误:This function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its de
查看>>
mysql长事务
查看>>
mysql问题记录
查看>>
mysql间隙锁
查看>>
MySQL集群解决方案(1):MySQL数据库的集群方案
查看>>