---
answer: direct
beat: system-design
source: 1 article · updated: November 17, 2026
---

Why did Atlassian's Aurora clusters fail to start even though replication looked healthy?

Aurora's startup process enumerates every file in the cluster volume as a health check, and PostgreSQL stores every table, index, and sequence as at least one separate file. With roughly 5,000 files per Jira tenant database and up to 4,000 tenants per cluster, that's around 20 million files to enumerate — a process slow enough to exceed Aurora's internal startup timeout, causing the instance to fail even though the underlying data had replicated correctly.

Answered in

The Migration Trick That Moved 4 Million Databases Without a Bigger Fleet

Atlassian couldn't provision enough spare capacity to migrate 4M Jira databases at once. So they made the migration feed itself — a daisy chain, not a fleet.

Crashtech Editorial November 17, 2026 System Design & Architecture

Read the full analysis

Other questions this article answers

More system design & architecture questions

Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the System Design & Architecture beat.