# Elasticsearch Input Plugin for Logstash 6.0.0 - Issue indexing data

**URL:** https://discuss.elastic.co/t/elasticsearch-input-plugin-for-logstash-6-0-0-issue-indexing-data/110054
**Category:** Logstash
**Created:** [December 3, 2017, 2:57pm UTC](https://discuss.elastic.co/t/elasticsearch-input-plugin-for-logstash-6-0-0-issue-indexing-data/110054 "2017-12-03T14:57:32Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![PixelatedFigure](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pixelatedfigure/32/24970_2.png) [@PixelatedFigure](https://discuss.elastic.co/u/PixelatedFigure)
#### Post date: [December 3, 2017, 2:57pm UTC](https://discuss.elastic.co/t/elasticsearch-input-plugin-for-logstash-6-0-0-issue-indexing-data/110054/1 "2017-12-03T14:57:32Z")

</div>

This issue regards ES Input Plugin for Logstash.

I am using Windows 10 and the new Logstash 6.0.0 version.  
I'm trying to run 2 pipelines -via the new pipeline.yml configuration- where the first one grabs the data from a database to index to ES, and the other takes the data indexed in ES and modifies it and re-indexes it to another ES index.

At first, since there's no data, the second pipeline returns an error 404, which is self explanatory since the data from the database haven't been imported to ES yet, but after the data goes into ES, it stops giving a 404, but at the same time doesn't do anything with the data.  
Once I restart logstash with the same configuration, AND with the data already existing in ES, it grabs it and modifies it and does what I want.

This seems like a faulty behavior to me, and I'd like to know some explanation for why is this happening, and if there is some sort of a way to make pipelines depend on each other or delay pipelines for a short period of time.

---

<div class="post-metadata">

### Author: ![JKhondhu](https://avatars.discourse-cdn.com/v4/letter/j/ed655f/32.png) [@JKhondhu](https://discuss.elastic.co/u/JKhondhu)
#### Post date: [December 5, 2017, 8:29am UTC](https://discuss.elastic.co/t/elasticsearch-input-plugin-for-logstash-6-0-0-issue-indexing-data/110054/2 "2017-12-05T08:29:58Z")

</div>

Hi,  
Can you share your pipeline.yml.

---

<div class="post-metadata">

### Author: ![PixelatedFigure](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pixelatedfigure/32/24970_2.png) [@PixelatedFigure](https://discuss.elastic.co/u/PixelatedFigure)
#### Post date: [December 6, 2017, 12:45pm UTC](https://discuss.elastic.co/t/elasticsearch-input-plugin-for-logstash-6-0-0-issue-indexing-data/110054/3 "2017-12-06T12:45:45Z")

</div>

Hello, the pipeline has only those following lines, the rest are comments:

```
- pipeline.id: source
  path.config: "/C:/fakepath/Logstash_Configuration/Source"
- pipeline.id: target
  path.config: "/C:/fakepath/Logstash_Configuration/Target"

```

As I mentioned, once I restart the Logstash session, after the data exist in ES, it works and it replicates the data with the modifications that I need.

---

<div class="post-metadata">

### Author: ![PixelatedFigure](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pixelatedfigure/32/24970_2.png) [@PixelatedFigure](https://discuss.elastic.co/u/PixelatedFigure)
#### Post date: [December 12, 2017, 10:53am UTC](https://discuss.elastic.co/t/elasticsearch-input-plugin-for-logstash-6-0-0-issue-indexing-data/110054/4 "2017-12-12T10:53:15Z")

</div>

The 404 error would stop happening if the index already existed, even without data, but the pipeline wont modify the data unless it was already in the index before starting the pipeline.

---

<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: [January 9, 2018, 10:55am UTC](https://discuss.elastic.co/t/elasticsearch-input-plugin-for-logstash-6-0-0-issue-indexing-data/110054/5 "2018-01-09T10:55:41Z")

</div>

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