-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/me/sites times out for users with thousands of sites #96640
Comments
OpenAI suggested the following labels for this issue:
|
Hi @dsas, I'm following up on the conversation here: p1732188303637839-slack-C07GZ2UA3TN and also from the p2 post here: pfVjQF-qC-p2 where we mention we'll have a data request to find out more about that, so we can consider how to prioritise this issue. Before reaching out to data team, I'd like to double check with you and see if there's any conversations/p2 going on with the data team at the moment? Or it's fine for us to reach out to data team and do a request directly? |
Haven't reached out yet @ouikhuan , it strikes me that it might have come up before but I haven't looked yet. I'm afk today but I'll look and ask tomorrow if no-one beats me to it. |
Commented here: pfVjQF-qC-p2#comment-147 |
Support References This comment is automatically generated. Please do not edit it.
|
Adjusting this priority to Normal - as a good fix to have, but not affecting too many users. |
Quick summary
See the parent issue for more information
/me/sites returns a HTTP 504 - gateway timeout for users with ~3000 sites.
/me/sites doesn't currently have pagination uggcf%3N%2S%2Suers.yv%2S%3Suggcf%3N%2S%2Sbcratebx.n8p.pbz%2Sfbhepr%2Skers%2Sjcpbz%2Schoyvp.ncv%2Serfg%2Sjcpbz%2Qwfba%2Qraqcbvagf%2Spynff.jcpbz%2Qwfba%2Qncv%2Qzr%2Qfvgrf%2Qraqcbvag.cuc%3Se%3Q5o812359%236-og It does have some performance instrumentation with statsd.
Steps to reproduce
What you expected to happen
A list of sites
What actually happened
A HTTP 504
Impact
One
Available workarounds?
No and the platform is unusable
If the above answer is "Yes...", outline the workaround.
No response
Platform (Simple and/or Atomic)
No response
Logs or notes
No response
The text was updated successfully, but these errors were encountered: