# File input v4.1.2 tailing - duplicate docs ingested

**URL:** <https://discuss.elastic.co/t/file-input-v4-1-2-tailing-duplicate-docs-ingested/130648>\
**Category:** Logstash\
**Created:** [May 4, 2018, 2:52pm UTC](https://discuss.elastic.co/t/file-input-v4-1-2-tailing-duplicate-docs-ingested/130648 "2018-05-04T14:52:08Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![guyboertje](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/guyboertje/32/31592_2.png) [@guyboertje](https://discuss.elastic.co/u/guyboertje)\
**Post date:** [May 9, 2018, 12:21pm UTC](https://discuss.elastic.co/t/file-input-v4-1-2-tailing-duplicate-docs-ingested/130648/5 "2018-05-09T12:21:47Z")

</div>

@ld_pvl

I want to work on this issue and the others you have open in one place.

1. This issue and the [read-to-eof-no-delimiter-found-in-current-chunk](https://discuss.elastic.co/t/logstash-6-2-4-read-to-eof-no-delimiter-found-in-current-chunk/130613) have the same origin in my opinion. It is a bug (I think) related how the plugin reacts to file rotations in the scheme used.

2. The [last outstanding issue you have](https://discuss.elastic.co/t/logstash-6-2-1-big-since-db-file-causes-outofmemory/129501) regards the very long time it takes to move from the discover phase to the processing phase when initially discovering 500,000 files.

I will look at both of these shortly. 1 can affect other users but 2 is more applicable to your use case.  
Both are extremely hard to writing failing test scenarios for though so patience is needed.

---

_[View the full topic](https://discuss.elastic.co/t/file-input-v4-1-2-tailing-duplicate-docs-ingested/130648)._