github-mirrors/logstash
1
0
Fork 0
mirror of https://github.com/elastic/logstash.git synced 2025-04-24 06:37:19 -04:00
Code Issues Projects Releases Packages Wiki Activity

Add info to docs about upgrading with persistent queues

Browse source 
Add fix from doc review

Fixes #7546
This commit is contained in:
DeDe Morton 2017-06-27 13:02:02 -07:00
parent 3a6902c2f3
commit ab0a52c554
1 changed files with 15 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

15
docs/static/upgrading.asciidoc vendored
View file

@ -16,6 +16,7 @@ See the following topics for information about upgrading Logstash:
* <<upgrading-using-package-managers>>
* <<upgrading-using-direct-download>>
* <<upgrading-logstash-pqs>>
* <<upgrading-logstash-5.0>>
[[upgrading-using-package-managers]]
@ -43,6 +44,20 @@ This procedure downloads the relevant Logstash binaries directly from Elastic.
some Logstash plugins have changed in the 5.x release.
5. Restart your Logstash pipeline after updating your configuration file.
[[upgrading-logstash-pqs]]
=== Upgrading with Persistent Queues Enabled
Upgrading Logstash with persistent queues enabled is supported. The persistent
queue directory is self-contained and can be read by a new Logstash instance
running the same pipeline. You can safely shut down the original Logstash
instance, spin up a new instance, and set `path.queue` in the `logstash.yml`
<<logstash-settings-file,settings file>> to point to the original queue directory.
You can also use a mounted drive to make this workflow easier.
Keep in mind that only one Logstash instance can write to `path.queue`. You
cannot have the original instance and the new instance writing to the queue at
the same time.
[[upgrading-logstash-5.0]]
=== Upgrading Logstash to 5.0