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

Delete room (admin-api) fails/timeouts before done. #17800

Open
olmari opened this issue Oct 7, 2024 · 0 comments
Open

Delete room (admin-api) fails/timeouts before done. #17800

olmari opened this issue Oct 7, 2024 · 0 comments

Comments

@olmari
Copy link
Contributor

olmari commented Oct 7, 2024

Description

When I use delete room through Synapse admin-api, no matter v1 or v2, if it is massive room, after some 4-6 hours (not really timed) or so the delete task will fail, despite there was being PSQL thread for delete for full load all that time... But if I just keep rerunning the task, eventually it will success.. Here is an excerpt from one room through v2 that I first tried couple times with v1 api, then with v2:

{
  "results": [
    {
      "delete_id": "UmVcAHOubayaZUVX",
      "status": "failed",
      "shutdown_room": null
    },
    {
      "delete_id": "eRURlGTxWZdZalLa",
      "status": "failed",
      "shutdown_room": null
    },
    {
      "delete_id": "vDZzfLohvBiHCJke",
      "status": "complete",
      "shutdown_room": {
        "kicked_users": [],
        "failed_to_kick_users": [],
        "local_aliases": [],
        "new_room_id": null
      }
    }
  ]
}

Steps to reproduce

  • Have massive room to delete
  • Hit /_synapse/admin/v2/rooms/<RoomID>
  • Wait.

Homeserver

hacklab.fi

Synapse Version

1.116.0

Installation Method

Debian packages from packages.matrix.org

Database

Single PSQL 17

Workers

Multiple workers

Platform

Debian 12, 8 core, 32g RAM Upcloud VM, 100k IOPS-

Configuration

Presence is enabled, MSCs for Hookshot E2E are enabled.

Relevant log output

Haven't found the relevant spot, but as the thing _eventually_ works, I'm 99.9% sure it is some form of timeout.

Anything else that would be useful to know?

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant