# \_bulk occasionally failing, not giving me enough info

**URL:** <https://discuss.elastic.co/t/-bulk-occasionally-failing-not-giving-me-enough-info/96491>\
**Category:** Elasticsearch\
**Created:** [August 9, 2017, 5:43pm UTC](https://discuss.elastic.co/t/-bulk-occasionally-failing-not-giving-me-enough-info/96491 "2017-08-09T17:43:12Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![roborich](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/roborich/32/20948_2.png) [@roborich](https://discuss.elastic.co/u/roborich)\
**Post date:** [August 9, 2017, 5:43pm UTC](https://discuss.elastic.co/t/-bulk-occasionally-failing-not-giving-me-enough-info/96491/1 "2017-08-09T17:43:12Z")

</div>

I am importing data from a csv -\> logstash -\> elasticsearch and about 1% of my data ends up vanishing.

Logstash doesn't have anything showing up in the logs.

However elasticsearch is showing this error for each missing piece of data.

```auto
[2017-08-09T13:31:17,720][DEBUG][o.e.a.b.TransportShardBulkAction] [z61oeaJ] [property][1] failed to execute bulk item (update) BulkShardRequest [[property][1]] containing [27] requests
org.elasticsearch.index.mapper.MapperParsingException: failed to parse
    at.org.elasticsearch...
    ...
    ...
Caused by: java.lang.IllegalArgumentException: Malformed content, found extra data after parsing: FIELD_NAME

```

I later added some code to remove fields with null values and last line of my error switched to.

```auto
Caused by: java.lang.IllegalArgumentException: Malformed content, found extra data after parsing: END_OBJECT

```

I tried upping my logging levels... but I can't seem to get any more information than this. Is there any way to know which field is the problem?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [August 10, 2017, 7:50am UTC](https://discuss.elastic.co/t/-bulk-occasionally-failing-not-giving-me-enough-info/96491/2 "2017-08-10T07:50:01Z")

</div>

Have you looked at the Logstash logs?

---

<div class="post-metadata">

**Author:** ![roborich](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/roborich/32/20948_2.png) [@roborich](https://discuss.elastic.co/u/roborich)\
**Post date:** [August 10, 2017, 5:24pm UTC](https://discuss.elastic.co/t/-bulk-occasionally-failing-not-giving-me-enough-info/96491/3 "2017-08-10T17:24:15Z")

</div>

Yes, they didn't have any information.

After digging around though the data,  
I found that the dropped documents all had geo\_points that had null lat, lon values. Every other parsing error I encountered was a lot more descriptive.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [August 10, 2017, 9:00pm UTC](https://discuss.elastic.co/t/-bulk-occasionally-failing-not-giving-me-enough-info/96491/4 "2017-08-10T21:00:26Z")

</div>

Please do create an issues on github so we can make the error more human friendly 🙂

---

<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:** [September 7, 2017, 9:00pm UTC](https://discuss.elastic.co/t/-bulk-occasionally-failing-not-giving-me-enough-info/96491/5 "2017-09-07T21:00:36Z")

</div>

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