# Documents missing after jdbc input to Elastic

**URL:** <https://discuss.elastic.co/t/documents-missing-after-jdbc-input-to-elastic/121166>\
**Category:** Logstash\
**Created:** [February 23, 2018, 5:16am UTC](https://discuss.elastic.co/t/documents-missing-after-jdbc-input-to-elastic/121166 "2018-02-23T05:16:47Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![johnjingle](https://avatars.discourse-cdn.com/v4/letter/j/87869e/32.png) [@johnjingle](https://discuss.elastic.co/u/johnjingle)\
**Post date:** [February 23, 2018, 5:16am UTC](https://discuss.elastic.co/t/documents-missing-after-jdbc-input-to-elastic/121166/1 "2018-02-23T05:16:47Z")

</div>

We have 50000000 records in SQL Server database and after using Logstash JDBC plugin to Elastic we are missing around 500 documents. Wondering what that might be.

---

<div class="post-metadata">

**Author:** ![johnjingle](https://avatars.discourse-cdn.com/v4/letter/j/87869e/32.png) [@johnjingle](https://discuss.elastic.co/u/johnjingle)\
**Post date:** [March 6, 2018, 3:23pm UTC](https://discuss.elastic.co/t/documents-missing-after-jdbc-input-to-elastic/121166/2 "2018-03-06T15:23:29Z")

</div>

This was done on AWS with a three node cluster and an AWS Elastic Load Balancer. A separate node for SQL Server and a separate node for Logstash. The ELB can (and does) dynamically change its IP address and I was wondering if this could be the cause.

---

<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:** [April 3, 2018, 3:23pm UTC](https://discuss.elastic.co/t/documents-missing-after-jdbc-input-to-elastic/121166/3 "2018-04-03T15:23:40Z")

</div>

Closed on April 3, 2018, 3:23pm UTC

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