No configuration found for this host:tier1
本文共 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 csv import meets charset
查看>>
multivariate_normal TypeError: ufunc ‘add‘ output (typecode ‘O‘) could not be coerced to provided……
查看>>
MySQL DBA 数据库优化策略
查看>>
multi_index_container
查看>>
mutiplemap 总结
查看>>
MySQL Error Handling in Stored Procedures---转载
查看>>
MVC 区域功能
查看>>
MySQL FEDERATED 提示
查看>>
mysql generic安装_MySQL 5.6 Generic Binary安装与配置_MySQL
查看>>
Mysql group by
查看>>
MySQL I 有福啦，窗口函数大大提高了取数的效率！
查看>>
mysql id自动增长 初始值 Mysql重置auto_increment初始值
查看>>
MySQL in 太多过慢的 3 种解决方案
查看>>
Mysql Innodb 锁机制
查看>>
MySQL InnoDB中意向锁的作用及原理探
查看>>
MySQL InnoDB事务隔离级别与锁机制深入解析
查看>>
Mysql InnoDB存储引擎 —— 数据页
查看>>
Mysql InnoDB存储引擎中的checkpoint技术
查看>>
Mysql InnoDB存储引擎中缓冲池Buffer Pool、Redo Log、Bin Log、Undo Log、Channge Buffer
查看>>
MySQL InnoDB引擎的锁机制详解
查看>>