# Logstash 2.3.0 causing problems with http es\_bulk inputs

**URL:** <https://discuss.elastic.co/t/logstash-2-3-0-causing-problems-with-http-es-bulk-inputs/45860>\
**Category:** Logstash\
**Created:** [March 31, 2016, 12:36am UTC](https://discuss.elastic.co/t/logstash-2-3-0-causing-problems-with-http-es-bulk-inputs/45860 "2016-03-31T00:36:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![esds2000](https://avatars.discourse-cdn.com/v4/letter/e/858c86/32.png) [@esds2000](https://discuss.elastic.co/u/esds2000)\
**Post date:** [March 31, 2016, 12:36am UTC](https://discuss.elastic.co/t/logstash-2-3-0-causing-problems-with-http-es-bulk-inputs/45860/1 "2016-03-31T00:36:39Z")

</div>

After upgrading to Logstash 2.3.0 our http input using the es\_bulk codec stopped working. The only data passing through to redis or elastic is the meta blob. Downgrading to 2.2.3 fixed the issue. Is this a bug with the new pipeline processing or am I missing a configuration that needs to be changed for this input now?

---

<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 6, 2017, 5:04am UTC](https://discuss.elastic.co/t/logstash-2-3-0-causing-problems-with-http-es-bulk-inputs/45860/2 "2017-07-06T05:04:39Z")

</div>