Skip to main content

Fire Arrow Server 2.1.1

· One min read
Till Gerken
Till Gerken
CTO

Fire Arrow Server 2.1.1 has been released.

  • (bugfix) The Azure production image no longer fails to start because of a duplicate binary-storage configuration key

Bug Fixes​

Azure production image crashed on startup​

Deployments using the Azure production image (fire-arrow-server-azure) from 2.1.0 could fail to start: the container exited during configuration loading before the server accepted any requests. On Azure App Service the site could still show as Running while the container silently crash-looped.

The shipped Azure configuration declared fire-arrow.binary-storage twice in the same YAML mapping. The YAML loader rejects duplicate keys, so Spring Boot aborted during environment preparation. The intent of that second declaration — enabling the orphan-blob garbage collector by default in the Azure image (BINARY_GC_ENABLED defaulting to true) — was already covered by the main binary-storage block; the stub was redundant and fatal.

2.1.1 removes the duplicate key and keeps the Azure-image default of BINARY_GC_ENABLED=true in the single canonical gc block. Deployments that set BINARY_GC_ENABLED explicitly are unchanged. Non-Azure images and custom configuration files that never carried this duplicate are unaffected.