BackendResponseTime on beta cluster is high when logged in
Open, Needs TriagePublic
Actions

Assigned To

None

Authored By

	Stang
	Nov 22 2022, 10:20 PM

Description

On production, wgBackendResponseTime is around 500ms but on beta cluster it's around 4000ms - there must be something wrong. This only happens if you are logged in to an account, and everything works fine in incognito mode.

Event Timeline

Stang created this task.Nov 22 2022, 10:20 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptNov 22 2022, 10:20 PM

TheresNoTime subscribed.Nov 22 2022, 10:25 PM

Reedy added a project: Performance Issue.Nov 22 2022, 10:32 PM

I can't see anything immediately obvious and new in the logs, and the backends seem as low on resources as normal… ~~perhaps we should just turn it off and on again?~~

Today I found I even could not access beta cluster...

Request from [redacted] via deployment-cache-text07 deployment-cache-text07, Varnish XID 30920951
Error: 503, Backend fetch failed at Wed, 30 Nov 2022 06:27:49 GMT

In T323655#8430662, @Stang wrote:
Today I found I even could not access beta cluster...
Request from [redacted] via deployment-cache-text07 deployment-cache-text07, Varnish XID 30920951
Error: 503, Backend fetch failed at Wed, 30 Nov 2022 06:27:49 GMT

Looks good to me now.
(FYI, I heard someone else also encountered "504 Gateway Timeout" error)

BackendResponseTime on beta cluster is high when logged inOpen, Needs TriagePublicActions

Description

Event Timeline

BackendResponseTime on beta cluster is high when logged in
Open, Needs TriagePublic
Actions