# Migrating from 5.6 to 6.6 and issue with persistent queue

**URL:** https://discuss.elastic.co/t/migrating-from-5-6-to-6-6-and-issue-with-persistent-queue/171507
**Category:** Logstash
**Created:** [March 8, 2019, 2:05pm UTC](https://discuss.elastic.co/t/migrating-from-5-6-to-6-6-and-issue-with-persistent-queue/171507 "2019-03-08T14:05:14Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![mw\_jko](https://avatars.discourse-cdn.com/v4/letter/m/db5fbb/32.png) [@mw\_jko](https://discuss.elastic.co/u/mw_jko)
#### Post date: [March 8, 2019, 2:05pm UTC](https://discuss.elastic.co/t/migrating-from-5-6-to-6-6-and-issue-with-persistent-queue/171507/1 "2019-03-08T14:05:15Z")

</div>

Hi there,

we are using a very simple one node ELK docker-compose based stack running on one server. Elasticsearch, Kibana, Logstash are all running version 5.6.3.

We use the persistent queue feature. I'm aware of the [logstash issue with persistent queues](https://www.elastic.co/guide/en/logstash/6.6/upgrading-logstash-pqs.html#upgrading-logstash-pqs) and I think I made the required change already in the past.

Both the "old" (and restarted/running) Logstash 5.6 and new 6.6 `config/logstash.yml` (queue related content):

```auto
queue.type: persisted
queue.drain: true
path.queue: /usr/share/logstash/queue

```

What we do:

1. copy 6.6 files to target directory
2. `docker-compose down --volumes --remove-orphans` (elasticsearch/logstash data is an external volume and will not be deleted)
3. `docker-compose build --pull`
4. `docker-compose up -d`

From what I read, the `queue.drain: true` should force the queue to drain when stopping the container, right?

Still, after the `up` the logstash keeps crashing/restarting:

```auto
[2019-03-08T13:36:56,607][INFO][org.logstash.ackedqueue.QueueUpgrade] No PQ version file found, upgrading to PQ v2.
[2019-03-08T13:36:56,861][ERROR][org.logstash.ackedqueue.QueueUpgrade] Logstash was unable to upgrade your persistent queue data.Please either downgrade to your previous version of Logstash and fully drain your persistent queue or delete your queue data.dir if you don't need to retain the data currently in your queue.
[2019-03-08T13:36:56,877][ERROR][org.logstash.execution.AbstractPipelineExt] Logstash failed to create queue.
java.lang.IllegalStateException: com.fasterxml.jackson.databind.exc.MismatchedInputException: Unexpected token (START_OBJECT), expected START_ARRAY: need JSON Array to contain As.WRAPPER_ARRAY type information for class java.util.HashMap
...

```

What am I missing? Is there a way to monitor the queue? Thank you in advance 🙂

---

<div class="post-metadata">

### Author: ![mw\_jko](https://avatars.discourse-cdn.com/v4/letter/m/db5fbb/32.png) [@mw\_jko](https://discuss.elastic.co/u/mw_jko)
#### Post date: [March 11, 2019, 10:31am UTC](https://discuss.elastic.co/t/migrating-from-5-6-to-6-6-and-issue-with-persistent-queue/171507/2 "2019-03-11T10:31:53Z")

</div>

Looks like I finally found the issue. The `queue.drain` setting can be found first in [6.0 logstash documentation](https://www.elastic.co/guide/en/logstash/6.0/persistent-queues.html) . (No word about this setting in 5.6). So it looks like I have to add at least one more step (5.6. -\> 6.0 -\> 6.6)

---

<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 8, 2019, 10:31am UTC](https://discuss.elastic.co/t/migrating-from-5-6-to-6-6-and-issue-with-persistent-queue/171507/3 "2019-04-08T10:31:55Z")

</div>

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