【问题标题】:sincedb_path /dev/null doesn't work因为db_path /dev/null 不起作用
【发布时间】:2017-09-24 19:25:34
【问题描述】:

我希望 Logstash 在没有新行时解析我的文件。

但它不起作用:

[2017-05-09T17:28:07,523][DEBUG][logstash.inputs.file     ] each: new inode: /exports/export4hadoop_FULL.csv: old inode was ["136139751", 0, 64769], new is 
["136139747", 0, 64769]
[2017-05-09T17:28:07,523][DEBUG][logstash.inputs.file     ] :delete for /exports/export4hadoop_FULL.csv, closing file
[2017-05-09T17:28:07,525][DEBUG][logstash.inputs.file     ] _open_file: /exports/export4hadoop_FULL.csv: opening
[2017-05-09T17:28:07,526][DEBUG][logstash.inputs.file     ] /exports/export4hadoop_FULL.csv: sincedb last value 985877, cur size 985877
[2017-05-09T17:28:07,526][DEBUG][logstash.inputs.file     ] /exports/export4hadoop_FULL.csv: sincedb: seeking to 985877

我的配置文件:

input {
 file {
  path => "/exports/export4hadoop_FULL.csv"
  start_position => "beginning"
  sincedb_path => "/dev/null"
 }
}

我没有在主目录下找到任何 .sincedb 文件。我不知道 Logstash 使用的 .sincedb 文件在哪里..

而且我不明白为什么它存储一个 .sincedb,因为我指定了 sincedb_path => "/dev/null"

谢谢你:)

【问题讨论】:

    标签: elasticsearch logstash bigdata


    【解决方案1】:

    sincedb_path 值默认使用的文件位于;

    LOGSTASH_HOME\data\plugins\inputs\file

    我建议您检查该文件夹是否有任何文件,删除它们并重新运行测试。

    【讨论】:

      猜你喜欢
      • 2018-05-11
      • 1970-01-01
      • 2018-05-05
      • 1970-01-01
      • 2013-02-17
      • 2017-07-11
      • 1970-01-01
      • 2016-05-02
      • 1970-01-01
      相关资源
      最近更新 更多