# Datafeed has missed documents due to ingest latency error **URL:** \ **Category:** Elasticsearch\ **Tags:** elastic-stack-machine-learning\ **Created:** [August 23, 2020, 12:32pm UTC](https://discuss.elastic.co/t/datafeed-has-missed-documents-due-to-ingest-latency-error/246016 "2020-08-23T12:32:05Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![sophie\_chang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sophie_chang/32/18008_2.png) [@sophie\_chang](https://discuss.elastic.co/u/sophie_chang)\ **Post date:** [August 24, 2020, 2:24pm UTC](https://discuss.elastic.co/t/datafeed-has-missed-documents-due-to-ingest-latency-error/246016/4 "2020-08-24T14:24:09Z")
Hi You need a node with an ingest role `i`. You should have one already in cloud. ```auto # GET _cat/nodes 127.0.0.1 70 80 1 0.00 0.03 0.05 dlm - node1 127.0.0.1 46 80 1 0.00 0.03 0.05 dlmt * node2 127.0.0.1 63 80 1 0.00 0.03 0.05 dilmt - node3 ``` With respect to load, please benchmark locally to see if there is a possible performance impact. You don't really need the painless script part from the blog example, and I doubt that the single `set` processor will make a noticeable difference - but it depends on your data and use case. Before you change your ingest, as a first step you could also try a manual validation that you have delayed data by running a search that will replicate what the delayed data check is trying to achieve. Assuming you have a `15m` `bucket_span` and a `30m` `query_delay`, create a date histogram search e.g. count of events every 15m from `now-90m` say. Manually refresh this periodically over the course of the next 90m and see if the counts change as time elapses. Pay particular attention to the counts from time buckets that are greater than 30m ago. If these are changing, this suggests an ingest latency. --- _[View the full topic](https://discuss.elastic.co/t/datafeed-has-missed-documents-due-to-ingest-latency-error/246016)._