Skip to content
This repository was archived by the owner on Apr 26, 2024. It is now read-only.
This repository was archived by the owner on Apr 26, 2024. It is now read-only.

Default sync_response_cache_duration can lead to clients never being able to initial sync #13027

@turt2live

Description

@turt2live

Description

Large accounts or slow servers can mean that the client will retry /sync (without ?since) until it gets a result. However, the server's default cache time for sync responses seemingly went from some number of minutes to zero. This means that the server processes large /sync requests in the background but immediately throws away the result if the client gave up waiting and tried a second request.

There should be a non-zero default on the config value.

Steps to reproduce

  • Be in thousands of rooms
  • Have a slow-ish server
  • Try to sync your account

Homeserver

t2l.io & t2bot.io

Synapse Version

1.60.0

Installation Method

pip (from PyPI)

Platform

N/A

Relevant log output

N/A

Anything else that would be useful to know?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    T-TaskRefactoring, removal, replacement, enabling or disabling functionality, other engineering tasks.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions