From ddbb6ad8394fae6d7eda138741ffe75fb00a2b4f Mon Sep 17 00:00:00 2001 From: Andrew Cholakian Date: Wed, 9 May 2018 13:50:19 -0500 Subject: [PATCH] Use @karenzone 's improved wording Fixes #9542 --- docs/static/breaking-changes.asciidoc | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/docs/static/breaking-changes.asciidoc b/docs/static/breaking-changes.asciidoc index 13ec9297d18..7fbf40f5d90 100644 --- a/docs/static/breaking-changes.asciidoc +++ b/docs/static/breaking-changes.asciidoc @@ -2,13 +2,11 @@ == Breaking Changes Across PQ Versions -If you are upgrading between Logstash versions and use the persistent queue, we strongly recommend draining or deleting -your persistent queue prior to the upgrade due to data incompatibilities. We are currently working on resolving these issues in our 6.3.0 release, but extra steps will need to be taken until then. +If you are upgrading Logstash and use the persistent queue, we strongly recommend that you drain or delete the persistent queue before you upgrade. -Drain the persistent queue be starting Logstash with the `queue.drain` setting enabled, followed by signalling Logstash to shutdown, then waiting for it to shutdown cleanly. This may take some time if you have a large queue backlog. - -This will not be the case when moving between versions greater than or equal to 6.3.0. +To drain the queue, enable the `queue.drain` setting, and then shutdown Logstash. Wait for it to shutdown completely. This may take a while if you have a large queue backlog. +We are working to resolve issues with data incompatibilities in our 6.3.0 release. These steps won’t be required when you upgrade to versions greater than or equal to 6.3.0. == Breaking Changes in 6.0.0