-
Notifications
You must be signed in to change notification settings - Fork 186
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
/hierarchy
pagination token is expiring too fast
#17340
Comments
According to this, the session has expired after 5 minutes and thus Synapse does not know about the token anymore. |
/hierarchy
returns 400 Unknown pagination token for a token that should be valid/hierarchy
pagination token is expiring too fast
Thanks for triaging and linking to the correct issue. Though apart from Element Web not doing the right thing, this is another failure mode and fallout from the /hierarchy endpoint being excruciatingly slow. |
I had plans to make it a lot faster by de-normalizing the space relationships to a separate table instead of having to parse it out of the state. You should be able to do some nice recursive queries on it. I seem to have not saved the branch for it though. |
Description
While searching a space via Element Desktop, I encountered a case where my homeserver returned 400 Unknown pagination token for a token that should've been valid, because it was returned as the
next_batch
in the immediately preceding/hierarchy
response.Steps to reproduce
Not sure how to reproduce. I just searched on a large space and waited.
Homeserver
termina.org.uk
Synapse Version
1.105.1
Installation Method
Other (please mention below)
Database
PostgreSQL
Workers
Single process
Platform
FreeBSD. Installed from the FreeBSD synapse package.
Configuration
No response
Relevant log output
Anything else that would be useful to know?
No response
The text was updated successfully, but these errors were encountered: