Just a FYI for people-- don’t try this upgrade during prime time. The 2.6.0b2 upgrade has been running on our server for well over 40 minutes when normally it takes just a couple of minutes, usually over before you check back. I was concerned it was broken, but logging into postgres I can see a hug…

A note on the extended Docker Manager and/or rebuild via SSH time has been added to the release notes.

[immagine] pfaffman: If there were a way to have ./launcher pass SKIP_POST_DEPLOYMENT_MIGRATIONS=1 into things without requiring an edit to the app.yml it’d make things less fiddly for the editor-challenged. Good idea, I went and implemented that: …

That is fantastic news! (Two other projects got in the way today and somehow my multisite instance is no longer working and playing well with S3. :crying_cat_face:) Thanks very much.

Is there a technical reason why post-upgrade DB changes need to be blocking by default? Is there any way to change that behavior so future upgrades get the site back up quickly and then run the post-upgrade stuff in the background? IMO anything essential for the upgraded application to function lik…

We started our rebuild from the command line seven hours ago! and is still going… It’s still here: [image] Any ideas? Edit: meanwhile I’ve killed the process to have the site live again for our users. But there has to be a better way to do this update.

[immagine] Paracelsus: We have 6 million posts I think they do :smiley::smiley::smiley:

[immagine] Paracelsus: there has to be a better way to do this update. Wait for this PR to be merged, then follow the steps listed: [immagine] 2.6.0b2 upgrade VERY slow installation Good idea, I went and implemented that:

[immagine] michaeld: [immagine] Paracelsus: We have 6 million posts I think they do :smiley::smiley::smiley: :smiley: :+1: About 100Gb :sunglasses: [immagine] jomaxro: Wait for this PR to be merged, then follow the steps listed: :+1: will do

So as I look at automating this upgrade, it occurs to me that knowing when to do this skip-post-deployment thing is rather complicated. For single-container installs, unless there is some bizarre migration (this is the first I’m aware of in my 4 years), there is no advantage to doing it this way. M…

Definitely not worth doing most of the time, but if your software’s upgrades rarely (but sometimes) take 10x as long as normal, that’s a real problem for a lot of users. After this I won’t run Discourse upgrades until at least a week post release. Of course you could argue that I’m a dumbass for no…

Aggiornamento 2.6.0b2 MOLTO lento

Supporto Installazione

pfaffman (Jay Pfaffman) 24 Agosto 2020, 4:28am 33

Non esattamente. Vedi Introducing Post Deployment Migration

Argomento		Risposte	Visualizzazioni
2.6.0 beta 3 update failed on disk and/or memory space Self-hosting server-resources	29	2528	Ottobre 26, 2020
An upgrade knocked my site offline; how long until it's restored? Self-hosting	16	357	Agosto 9, 2025
Upgrade failed spectacularily Support	25	719	Febbraio 10, 2025
Problem rebuilding because of slow database shutdown Self-hosting	26	1161	Aprile 25, 2023
Discourse upgrade via Web UI Fails & SSH Upgrade Brings Down Discourse Instance Self-hosting	17	2003	Novembre 26, 2021

Aggiornamento 2.6.0b2 MOLTO lento

Argomenti correlati