# Stopping trying to execute pipeline for document not on current index

**URL:** <https://discuss.elastic.co/t/stopping-trying-to-execute-pipeline-for-document-not-on-current-index/188473>\
**Category:** Elasticsearch\
**Created:** [July 2, 2019, 10:08am UTC](https://discuss.elastic.co/t/stopping-trying-to-execute-pipeline-for-document-not-on-current-index/188473 "2019-07-02T10:08:35Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![EldrosKandar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eldroskandar/32/33188_2.png) [@EldrosKandar](https://discuss.elastic.co/u/EldrosKandar)\
**Post date:** [July 2, 2019, 10:08am UTC](https://discuss.elastic.co/t/stopping-trying-to-execute-pipeline-for-document-not-on-current-index/188473/1 "2019-07-02T10:08:35Z")

</div>

I've been looking into one of the most recent log file (.i.e the log entries for one day) and I've found about 295 log entry similar to the following:

> [DEBUG][o.e.a.b.TransportBulkAction] [es-1] failed to execute pipeline [lgw] for document [index-2019.06.27/doc/null]

There are even entries for document in index which are already long gone!

How can I stop pipeline execution, if there are not at most directed to the index of the day before the current day?

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [July 2, 2019, 11:07am UTC](https://discuss.elastic.co/t/stopping-trying-to-execute-pipeline-for-document-not-on-current-index/188473/2 "2019-07-02T11:07:53Z")

</div>

hey,

how about a processor that checks in your pipeline for the date of the timestamp that the document provided? If that is older than X, you could use the drop processor.

--Alex

---

<div class="post-metadata">

**Author:** ![EldrosKandar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eldroskandar/32/33188_2.png) [@EldrosKandar](https://discuss.elastic.co/u/EldrosKandar)\
**Post date:** [July 2, 2019, 12:06pm UTC](https://discuss.elastic.co/t/stopping-trying-to-execute-pipeline-for-document-not-on-current-index/188473/3 "2019-07-02T12:06:40Z")

</div>

That could be interesting, is there a way to set that globally? I have about half a dozen pipeline I'll need to update.

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [July 2, 2019, 1:02pm UTC](https://discuss.elastic.co/t/stopping-trying-to-execute-pipeline-for-document-not-on-current-index/188473/4 "2019-07-02T13:02:31Z")

</div>

no, pipelines can be configured on a per-index base though.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 30, 2019, 1:02pm UTC](https://discuss.elastic.co/t/stopping-trying-to-execute-pipeline-for-document-not-on-current-index/188473/5 "2019-07-30T13:02:40Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.