Skip to content
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

Sync is timing out when I log in with a user who has many rooms #22457

Closed
chagai95 opened this issue Jun 6, 2022 · 6 comments
Closed

Sync is timing out when I log in with a user who has many rooms #22457

chagai95 opened this issue Jun 6, 2022 · 6 comments
Labels
T-Defect X-Needs-Info This issue is blocked awaiting information from the reporter

Comments

@chagai95
Copy link
Contributor

chagai95 commented Jun 6, 2022

Steps to reproduce

  1. Log in with a user with many rooms.

Outcome

What did you expect?

The sync should work

What happened instead?

It did not work.

Operating system

Ubuntu

Browser information

Chrome Version 100.0.4896.127 (Official Build) (64-bit)

URL for webapp

https://element.chagai.website/

Application version

1.10.8

Homeserver

Https://mx.chagai.website

Will you send logs?

Yes

@t3chguy
Copy link
Member

t3chguy commented Jun 6, 2022

A timeout would be an issue on the server side rather than the client, no?

@t3chguy t3chguy added the X-Needs-Info This issue is blocked awaiting information from the reporter label Jun 6, 2022
@chagai95
Copy link
Contributor Author

chagai95 commented Jun 6, 2022

I was thinking maybe it could wait longer if it is setting the timeout, is it not?

matrix-org/synapse#12971

@t3chguy
Copy link
Member

t3chguy commented Jun 6, 2022

The underlying http library will be timing out based on whether the server is sending keepalives. Element will keep retrying sync, in theory the server should continue the operation in the background and eventually respond to one of the newer requests.

Is the timeout variable set from Element? Maybe it needs to be higher?

This is not the same thing. Please refer to the spec.
https://spec.matrix.org/v1.2/client-server-api/#get_matrixclientv3sync

The maximum time to wait, in milliseconds, before returning this request. If no events (or other data) become available before this time elapses, the server will return a response with empty fields.

This only applies if there is no data to send, i.e the long-polling effect.

@chagai95
Copy link
Contributor Author

chagai95 commented Jun 6, 2022

ok thanks! I saw the 504 and thought it's an error...

@chagai95 chagai95 closed this as completed Jun 6, 2022
@t3chguy
Copy link
Member

t3chguy commented Jun 6, 2022

A 504 is an error, it is the (reverse) proxy timing out before the application does. /sync timeouts result in an empty response as per the spec. It'd be a 200, not a 504.

If no events (or other data) become available before this time elapses, the server will return a response with empty fields.

@chagai95
Copy link
Contributor Author

chagai95 commented Jun 6, 2022

ah ok thx for explaining!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-Defect X-Needs-Info This issue is blocked awaiting information from the reporter
Projects
None yet
Development

No branches or pull requests

2 participants