Page MenuHomePhabricator

Wind Down Phacility Operations
Open, NormalPublic

Assigned To
Authored By
May 29 2021, 8:50 PM
"Heartbreak" token, awarded by holmboe."Heartbreak" token, awarded by dtf."Heartbreak" token, awarded by Bezalel."Heartbreak" token, awarded by tiguchi."Heartbreak" token, awarded by krisbuist."Heartbreak" token, awarded by Krinkle."Heartbreak" token, awarded by radiantws."Heartbreak" token, awarded by seshness."Heartbreak" token, awarded by cspeckmim."Heartbreak" token, awarded by jbrownEP."Heartbreak" token, awarded by syncer."Heartbreak" token, awarded by d.maznekov."Heartbreak" token, awarded by HuMMeL621."Heartbreak" token, awarded by Info-Screen."Heartbreak" token, awarded by tycho.tatitscheff."Heartbreak" token, awarded by avivey."Heartbreak" token, awarded by siepkes."Heartbreak" token, awarded by 20after4."Heartbreak" token, awarded by chrisbolt."Heartbreak" token, awarded by eadler."Heartbreak" token, awarded by thoughtpolice."Heartbreak" token, awarded by hskiba."Heartbreak" token, awarded by leoluk."Heartbreak" token, awarded by stwalkerster."Heartbreak" token, awarded by faulconbridge."Heartbreak" token, awarded by olexiy.myronenko."Heartbreak" token, awarded by richardvanvelzen."Heartbreak" token, awarded by cburroughs.



"Secure" Service Tier is currently 4 hosts. This setup was to test repository clustering and database partitioning, and is not load related. secure can be scaled down to one host.

secure002 and secure004 are likely easy to take out of service, since they're pure replicas. Repositories can be stripped off secure003 easily, but the writable Files master database is on that host and the datasize isn't trivial (~8GB). This is probably easiest to deal with by just taking down services, dumping and moving the data, and accepting a couple hours of downtime.

The services on secure could conceivably be merged to admin, although I think the bootstrapping problem this creates is probably not worthwhile.


I'm planning to simply delete the Discourse forum without preserving any content. I think most of the useful content (e.g., bug reports with reproduction instructions) made it upstream, and the stuff that didn't make it upstream is largely not worth preserving.

Revisions and Commits

rP Phabricator

Event Timeline

epriestley triaged this task as Normal priority.May 29 2021, 8:50 PM
epriestley created this task.
epriestley added a commit: Restricted Diffusion Commit.May 29 2021, 8:57 PM
epriestley added a commit: Restricted Diffusion Commit.
epriestley added a commit: Restricted Diffusion Commit.May 29 2021, 9:58 PM

secure002 and secure004 are likely easy to take out of service, since they're pure replicas.

Just for my own notes: I pulled secure002 and secure004 out of the Almanac service definition, the notification and database cluster definitions, and the slb and snlb pools. I stopped them and nothing seemed broken, so I terminated them and nuked DNS.

HuMMeL621 added a subscriber: HuMMeL621.

Was a pleasure, thank you for this project!

Sorry to hear that and hope everything is OK with you @epriestley.
I spent many hours learning from this high-quality code base.
Best of luck in whatever you do in the future.