Skip to content

docs: list the 2026-11-10 index builds and migrations with measured times [ENG-2184] - #41

Draft
twk3 wants to merge 1 commit into
mainfrom
docs/eng-2184-upgrade-index-and-migration-impact
Draft

twk3 wants to merge 1 commit into
mainfrom
docs/eng-2184-upgrade-index-and-migration-impact

Conversation

@twk3

@twk3 twk3 commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

Owner: @twk3

Linear: ENG-2184

Merge after #39. This section links to #39's "Index Builds Before an Upgrade" and "Building the Indexes First" rather than repeating its commands, so until #39 merges those links lead nowhere.

Changes

  • docs/upgrading.md: a new section, "Upgrading from 2026-10-14 to 2026-11-10":
    • the six indexes the scheduler builds and the five migrations it runs, each with the time measured in the rehearsal;
    • what an operator does about the duplicate-key warnings from the API key and record key hash backfills;
    • when the docs: check what an upgrade's index builds cost before starting it [ENG-1881] #39 check can stop an upgrade: only a large orchestrationSession collection, about 18 GB at the default rate;
    • a line for installs still on 2026-07-26.
  • The Rollback section says rolling back to 2026-10-14 builds and drops nothing.
  • on-prem/CHANGELOG.md: two [Unreleased] Upgrade Notes. feat: add the ai-queue-worker service [ENG-2181] #40 also adds [Unreleased] entries, so expect a small merge there.

The headings use 2026-11-10, after the release candidate release/2026-11-10-003. If the release ships under another date, rename the heading and its two anchors.

How the numbers were measured

The full results are in the comment on ENG-2184.

  • Compose install of on-prem/2026-10-14-002, seeded with 3.1M instances (41 GB), 310k runs, 1.1M testRecord and 124k orchestrationSession.
  • Upgraded to images built from release/2026-11-10-003, with feat: add the ai-queue-worker service [ENG-2181] #40's Compose files.
  • docs: check what an upgrade's index builds cost before starting it [ENG-1881] #39's index-plan --gate exited 0 with a 25-second estimate. The scheduler logged Startup tasks complete 18 s after docker compose up -d, and the orchestrationSession build took 1.1 s with a cold cache.
  • All services came up and /health answered 200. Afterwards the plan had nothing pending.
  • Starting the 2026-10-14-002 scheduler on the upgraded database built and dropped nothing.

Checklist

  • PR title is Changelog-friendly: (fix|feat|chore): title [CSR-xxx]
  • User-friendly and meaningful description of the changes
  • Documentation was updated

🤖 Generated with Claude Code


Autofix with [code]smith
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.

…imes [ENG-2184]

Measured on a 2026-10-14-002 Compose install with 3.1M instances,
upgraded to release/2026-11-10-003: the scheduler finished startup 18 s
after `docker compose up -d`, and rolling back to 2026-10-14 built and
dropped nothing.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@baz-reviewer

baz-reviewer Bot commented Nov 12, 2026 •

Copy link
Copy Markdown

Review this PR on Baz

Baz Summary

Document the 2026-10-14 to 2026-11-10 upgrade path, covering the scheduler’s MongoDB index builds, migrations, measured startup impact, pre-upgrade checks, duplicate-key remediation, and rollback behavior. Update the upgrade guide and on-prem changelog so operators can assess and safely execute the release upgrade.

Latest Contributors(1)
UserCommitDate
dj@currents.devdocs: list the 2026-11...November 12, 2026


Skills  Activate Skill Maintainer to keep your skills up to date

Planner  This PR would have been improved with Baz Planner - Try it now

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant