Page MenuHomePhabricator

Implement brownout logic for dumps v1 on dumps web interface
Closed, ResolvedPublic

Description

To allow a graceful transition from dumps v1 to v2, we'd like to (broadly announce and then) introduce partial unavailability of v1.

This would be at the end of an upcoming month, when fewer downloads happen, then progressing towards the start of the month, and repeating as long as the migration lasts.

This ticket tracks the development of the Nginx config changes to enable that, for the v1 dumps in scope to be replaced by v2.

Acceptance criteria

  • The dumps web interface can serve HTTP 404 responses on particular days of the month, with at least 3 possible configurations: the last 25 days of the month, or last 15, or last 5.
  • The 404 response has a link to a (to be published) Wikitech documentation page.
  • This only applies to the dumps in scope for migration to v2.

Event Timeline

We'd like this to be done ideally still in September, but early October is reasonable.

The intention is to have this logic applied at the end of October, that is, blocking v1 downloads for the last N days of that month.

BTullis triaged this task as High priority.

Change #1346007 had a related patch set uploaded (by Btullis; author: Btullis):

[operations/puppet@production] dumps: web: Add a brownout for v1 meta-current and meta-history

https://gerrit.wikimedia.org/r/1346007

Change #1346007 merged by Btullis:

[operations/puppet@production] dumps: web: Add a brownout for v1 meta-current and meta-history

https://gerrit.wikimedia.org/r/1346007

Change #1353019 had a related patch set uploaded (by Btullis; author: Btullis):

[operations/puppet@production] dumps: Enable brownout for dumps v1 history from 2026-10-26

https://gerrit.wikimedia.org/r/1353019

Change #1353019 merged by Btullis:

[operations/puppet@production] dumps: Enable brownout for dumps v1 history from 2026-10-26

https://gerrit.wikimedia.org/r/1353019

I checked the CPU/load for the servers after merging the regex patch to the nginx.conf and any increase is negligible and could be background noise.

I'll resolve this ticket now, as we believe it to be done, but I will make a mental note to check on the 404 responses from October 26th.