Blixt Documentation v2.11

Before you upgrade

  1. Check Release-specific steps below for every release between yours and the target.
  2. Back up the index database. See Backup and recovery.
  3. Choose a quiet time. Clients see a short interruption while servers restart.

Docker

docker pull blixtfs/standard:latest
docker stop -t 90 blixt && docker rm blixt
# Run your usual docker run command with the new tag.

-t 90 gives BlixtFS time to finish uploading staged writes before Docker kills it; it waits up to file.shutdown_drain_seconds (default 60). See Stopping and upgrading.

On startup BlixtFS brings the index database up to the schema the new release expects. Writes that were staged but not yet uploaded when the old container stopped are uploaded by the new one.

With Docker Compose, set stop_grace_period: 90s on the service, change the image tag in compose.yaml, then:

docker compose pull && docker compose up -d

Kubernetes

helm upgrade bfs ./blixtfs -n bfs --reuse-values --set image.tag=2.11.0

Kubernetes replaces pods one at a time, and clients reconnect as servers come back.

Schema versions

BlixtFS versions its own index schema and evolves it in place.

Release-specific steps

2.11.0

2.11.0 upgrades the index database of earlier releases in place on its first start, with nothing to run by hand. On a large database built before 2.10, that first start takes longer.

A Spanner database built before 2.9 can’t be upgraded: 2.11.0 refuses it, with a message that it has to be dropped and re-created.

Rolling back

Schema changes cannot be rolled back automatically. Please contact support for assistance.

Checking the result

  • The startup banner shows the new version: docker logs blixt | grep "Blixt File System"
  • Clients can list and read files.
  • No errors in the log, and uploads are draining (see Monitoring).