it is going by inode. hence it is not reading it because logstash thinks it has already read file sitting on same inode.
check mode detail explanation that I put, as I had exact same problem
it is going by inode. hence it is not reading it because logstash thinks it has already read file sitting on same inode.
check mode detail explanation that I put, as I had exact same problem
© 2020. All Rights Reserved - Elasticsearch
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.