Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-24 09:28:54 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 60

Add note about downtime during database migrations (#2279)

Browse source 
This should help clarify that migrations should be run with server
instances stopped.
This commit is contained in:
Zachary Wasserman 2020-08-06 17:16:23 -07:00 committed by GitHub
parent c6ce648fef
commit 09632fb1ed
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
docs/infrastructure/updating-fleet.md
View file

@ -46,7 +46,13 @@ docker pull kolide/fleet
## Running database migrations
Before running the updated server, perform necessary database migrations:
Before running the updated server, perform necessary database migrations. It is always advised to back up the database before running migrations.
Database migrations in Fleet are intended to be run while the server is offline. Osquery is designed to be resilient to short downtime from the server, so no data will be lost from `osqueryd` clients in this process. Even on large Fleet installations, downtime during migrations is usually only seconds to minutes.
First, take the existing servers offline.
Run database migrations:
```
fleet prepare db
@ -54,7 +60,7 @@ fleet prepare db
Note, if you would like to run this in a script, you can use the `--no-prompt` option to disable prompting before the migrations.
The updated Fleet server should now be ready to run:
Start new Fleet server instances:
```
fleet serve