# Logstash with queue enabled not ack http input events after jdbc input runs

**URL:** <https://discuss.elastic.co/t/logstash-with-queue-enabled-not-ack-http-input-events-after-jdbc-input-runs/96358>\
**Category:** Logstash\
**Created:** [August 9, 2017, 1:47am UTC](https://discuss.elastic.co/t/logstash-with-queue-enabled-not-ack-http-input-events-after-jdbc-input-runs/96358 "2017-08-09T01:47:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![bearhead](https://avatars.discourse-cdn.com/v4/letter/b/87869e/32.png) [@bearhead](https://discuss.elastic.co/u/bearhead)\
**Post date:** [August 9, 2017, 1:47am UTC](https://discuss.elastic.co/t/logstash-with-queue-enabled-not-ack-http-input-events-after-jdbc-input-runs/96358/1 "2017-08-09T01:47:57Z")

</div>

Hi

I'm using logstash with queuing enabled.

I've setup logstash to inject rows from mysql via the mysql input plugin on startup. Currently this is injecting 1846 rows.

I also have a http input.

When I take down ES and restart logstash as expected I get errors

> logstash\_1 WARN logstash.outputs.amazones - Failed to flush outgoing items {:outgoing\_count=\>1, :exception=\>"Faraday::ConnectionFailed", :backtrace=\>nil}  
> logstash\_1 ERROR logstash.outputs.amazones - Attempted to send a bulk request to Elasticsearch configured at ...

I'd expect when in this situation hitting the logstash http input would result in an ack.

Actually the http POST does not return and the injection is not seen in logstash logs.

My logstash.yaml looks like

```
queue {
  type: persisted
  checkpoint.writes: 1
  queue.max_bytes: 8gb
  queue.page_capacity: 512mb
}

```

And my logstash.conf

```
input {

  jdbc {
    jdbc_connection_string => "${JDBC_CONNECTION_STRING}"
    jdbc_user => "${JDBC_USER}"
    jdbc_password => "${JDBC_PASSWORD}"
    jdbc_driver_library => "/home/logstash/jdbc_driver.jar"
    jdbc_driver_class => "com.mysql.jdbc.Driver"
    statement => "
     	SELECT blah blah blah
    "
  }

  http {
    host => "0.0.0.0"
    port => 31311
  }
}

output {
  stdout { codec => json_lines }
  amazon_es {
    hosts => ["${AWS_ES_HOST}"]
    region => "${AWS_REGION}"
    aws_access_key_id => '${AWS_ACCESS_KEY_ID}'
    aws_secret_access_key => '${AWS_SECRET_ACCESS_KEY}'
    "index" => "${INDEX_NAME}"
    "document_type" => "data"
    "document_id" => "%{documentid}"
  }
}

```

Is it possible for the http input to still ack events as I'm pretty sure the queue cannot be full as each event payload is about 850 characters?

Thanks in advance

---

<div class="post-metadata">

**Author:** ![bearhead](https://avatars.discourse-cdn.com/v4/letter/b/87869e/32.png) [@bearhead](https://discuss.elastic.co/u/bearhead)\
**Post date:** [August 15, 2017, 12:49am UTC](https://discuss.elastic.co/t/logstash-with-queue-enabled-not-ack-http-input-events-after-jdbc-input-runs/96358/2 "2017-08-15T00:49:28Z")

</div>

bump?

---

<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 12, 2017, 12:49am UTC](https://discuss.elastic.co/t/logstash-with-queue-enabled-not-ack-http-input-events-after-jdbc-input-runs/96358/3 "2017-09-12T00:49:47Z")

</div>

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