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

Presence worker gets stuck on 1.33.0rc1 #9899

Closed
tulir opened this issue Apr 28, 2021 · 5 comments · Fixed by #9900
Closed

Presence worker gets stuck on 1.33.0rc1 #9899

tulir opened this issue Apr 28, 2021 · 5 comments · Fixed by #9900
Labels
S-Major Major functionality / product severely impaired, no satisfactory workaround. T-Defect Bugs, crashes, hangs, security vulnerabilities, or other reported issues. X-Regression Something broke which worked on a previous release

Comments

@tulir
Copy link
Member

tulir commented Apr 28, 2021

Description

A line like this is spammed in the logs and the worker handling presence pins the CPU and gets stuck:

2021-04-28 12:05:20,199 - synapse.replication.tcp.resource - 187 - INFO - replication_notifier-103- Streaming: presence_federation -> 5

If presence is on the master process, then the master process gets stuck.

The issue goes away after disabling presence.

Steps to reproduce

  • Have presence and workers enabled
  • Update to 1.33.0rc1
  • Optionally, move the presence stream to a worker

Version information

  • Version: 1.33.0rc1
  • Install method: Docker
@deepbluev7
Copy link
Contributor

deepbluev7 commented Apr 28, 2021

Happens to me too shortly after updating. I installed from source. After I restarted it twice I can't reproduce it anymore though?

@erikjohnston erikjohnston added S-Major Major functionality / product severely impaired, no satisfactory workaround. T-Defect Bugs, crashes, hangs, security vulnerabilities, or other reported issues. X-Regression Something broke which worked on a previous release labels Apr 28, 2021
@erikjohnston
Copy link
Member

FTR disabling presence is a temporary fix, if you don't want to downgrade.

@deepbluev7
Copy link
Contributor

Logs from the start of the spam:

2021-04-28 11:40:39,306 - synapse.access.http.9893 - 387 - INFO - POST-111 - 127.0.0.1 - 9893 - {None} Processed request: 0.005sec/-0.000sec (0.002sec, 0.000sec) (0.001sec/0.002sec/5) 4B 200 "POST /_synapse/replication/fed_send_edu/m.presence/nCmfebTyOS HTTP/1.1" "Synapse/1.33.0rc1" [0 dbevts]
2021-04-28 11:40:39,307 - synapse.replication.tcp.resource - 187 - INFO - replication_notifier-59 - Streaming: presence -> 110906303
2021-04-28 11:40:39,328 - synapse.replication.tcp.resource - 187 - INFO - replication_notifier-60 - Streaming: presence_federation -> 1
2021-04-28 11:40:39,329 - synapse.replication.tcp.resource - 187 - INFO - replication_notifier-61 - Streaming: presence_federation -> 2
2021-04-28 11:40:39,331 - synapse.replication.tcp.resource - 187 - INFO - replication_notifier-62 - Streaming: presence_federation -> 3
2021-04-28 11:40:39,334 - synapse.replication.tcp.resource - 187 - INFO - replication_notifier-63 - Streaming: presence_federation -> 4
2021-04-28 11:40:39,351 - synapse.replication.tcp.resource - 187 - INFO - replication_notifier-64 - Streaming: presence_federation -> 4
2021-04-28 11:40:39,366 - synapse.replication.tcp.resource - 187 - INFO - replication_notifier-64 - Streaming: presence_federation -> 4
2021-04-28 11:40:39,382 - synapse.replication.tcp.resource - 187 - INFO - replication_notifier-64 - Streaming: presence_federation -> 4

@erikjohnston
Copy link
Member

Can someone try this with DEBUG logging on, at least for synapse.replication.tcp.resource please? I'm interested in log lines like: Getting stream: presence_federation: 2 -> 3

erikjohnston added a commit that referenced this issue Apr 28, 2021
Only affects workers. Introduced in #9819.

Fixes #9899.
@erikjohnston
Copy link
Member

#9900 should hopefully fix this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
S-Major Major functionality / product severely impaired, no satisfactory workaround. T-Defect Bugs, crashes, hangs, security vulnerabilities, or other reported issues. X-Regression Something broke which worked on a previous release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants