The following commit should improve the performance and reduce the number of 502 errors.
It helps a lot!
Thanks
I’m still seeing these errors, I’m afraid 
Yep, still appears from time to time.
502 errors on moving 5 messages.
5 posts in a PM? That’s weird. Is this a standard installation on Digital Ocean? Which kind of droplet?
Hi,
I tired to move 5 message from thread of 26 messages to thread with 200+ messages. 502!
Then I tried to move 2 of 2 messages to another thread with 1000+ messages. 502!
I do have standard Digital Ocean installation.
4 vCPUs / 8 GB Memory / 160 GB Disk + 200 GB / LON1
Forum statistics
Last 7 Last 30 All Time
Topics 101 486 11.0k
Posts 10.8k 45.0k 1.3M
Users 45 212 4.7k
Active Users 1.9k 2.3k —
Likes 12.4k 50.9k 1.0M
@gerhard is this the expensive post topic number remapping work?
It could also be the updating of quotes that was added recently. There were no new reports of 502 errors until that was added. I’ll have a look. It’s probably time to move all the resource intensive work into a background job.
Status update!
2.4.0.beta8 was good in term of 502 moving errors.
2.4.0.beta9 is terrible. Every move attempts gives 502.
I feel like this is something we need to get sorted, we have some customer complaints about poor performance here as well.
@kris.kotlarek can you bump this to the front of your list this week to have a quick look.
Great to see, as we were having a lot of trouble with this issue.
Will there by any way to change the timeout settings down the road? I notice that most of my 502 errors come when trying to move content out of a highly-populated topic.
Thanks all for addressing this problem.
Facendo seguito a quanto precede, nessun errore 502 dall’ultimo aggiornamento. Non sono sicuro di cosa sia cambiato, ma lo apprezzo comunque.
Saluti!
Well, not to be that guy, but…it’s back.
Scenario: user posts a video mistakenly in our “Pictures only” topic which has 5100+ posts containing images. I attempt to move that video to our “Videos only” topic, but I have started receiving the “502 error” message again.
This also happened a few days ago when trying to move some images from another topic into our “Pictures only” topic.
Could it have to do with the size of the originating topic at all? Does Discourse need to index or read the entire topic before moving the offending post to another location? It does seem to be the one originating topic that gives us the most trouble when we try to make a move.
We’re hosted with AWS if that matters.
Thanks for any guidance.
Bill
Abbiamo lo stesso problema da circa due settimane. È possibile ricompilare con una versione stabile?
Non ricordo più quale fosse l’ultima versione in cui questo non era un problema, né se sia la dimensione del nostro argomento a causare il problema.
Ho risolto questo problema. Il nostro server utilizzava solo circa 2 GB di memoria, ma il nostro VPS ne ha 16 GB. Quando ho provato a spostare un post, ho visto che PostgreSQL utilizzava molta CPU, ma l’utilizzo della memoria non cambiava. Dopo aver modificato il parametro db_shared_buffers nel file di configurazione del container e aver ricompilato l’applicazione, il problema 502 è stato risolto.
Proviamo il tuo metodo e facciamo rapporto. Apprezziamo!
Questo problema è tornato: errore 502 quando si spostano solo 5 post in un argomento esistente.
Sto cercando di spostare 5 post a partire da questo.
L’argomento di origine contiene oltre 7.000 messaggi.
Posso confermare che nell’ultima versione c’è questo problema (anche se non c’è alcun carico sul server)
Nel mio caso, l’argomento di destinazione ha 7.000 risposte e non riesco a spostare un singolo post da un argomento senza risposte. Errore 502.