Page MenuHomePhabricator

Update SchemaQuery and the web UI to accommodate multiple master databases
ClosedPublic

Authored by epriestley on Nov 12 2016, 5:27 PM.
Tags
None
Referenced Files
F15525254: D16847.id40575.diff
Mon, Apr 21, 1:08 PM
F15496726: D16847.id40569.diff
Sun, Apr 13, 7:48 AM
F15485764: D16847.id40569.diff
Thu, Apr 10, 2:10 AM
F15482681: D16847.id.diff
Wed, Apr 9, 7:12 AM
F15482133: D16847.id40575.diff
Wed, Apr 9, 3:18 AM
F15479407: D16847.diff
Tue, Apr 8, 6:55 AM
F15403927: D16847.id.diff
Mar 18 2025, 5:34 AM
F15389436: D16847.id40569.diff
Mar 15 2025, 5:15 AM
Subscribers
None

Details

Summary

Depends on D16115. Ref T11044. In the brave new world of multiple masters, we need to check the schemata on each master when looking for missing storage patches, keys, schema changes, etc.

This realigns all the "check out what's up with that schema" calls to work for multiple hosts, and updates the web UI to include a "Server" column and allow you to browse per-server.

This doesn't update bin/storage, so it breaks things on its own (and unit tests probably won't pass). I'll update that in the next change.

Test Plan

Configured local environment in cluster mode with multiple masters, saw both hosts' status reported in web UI.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable