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

Inbound federation worker began spinning CPU after a surge in federation traffic #11863

Closed
Half-Shot opened this issue Jan 31, 2022 · 4 comments
Labels
X-Needs-Info This issue is blocked awaiting information from the reporter

Comments

@Half-Shot
Copy link
Collaborator

Half-Shot commented Jan 31, 2022

Description

After a restart, it became fine again. I couldn't find a specific issue for "federation stops, cpu spins", so here is one.

image
image

Steps to reproduce

  • Have a host
  • Have lots of incoming traffic because the host runs a major IRC bridge.
  • CPU spins itself to death (>100% usage)
  • EDU traffic drops to near zero, reports of host feeling "broken".

Version information

  • Homeserver: libera.ems.host (Note, this host is only used by the bridge a.k.a all federation traffic, no sync traffic)
  • Version: 1.50.0
  • Install method: N/A
  • Platform: EMS

link to logs

@Half-Shot Half-Shot changed the title DRAFT: Inbound federation worker began spinning CPU while not processing incoming transactions Inbound federation worker began spinning CPU after a surge in federation traffic Jan 31, 2022
@clokep
Copy link
Member

clokep commented Feb 1, 2022

I think this has some overlap with #11818, but I'm unsure it is an identical issue. @Half-Shot any idea if this was from the same event? Doesn't seem like it since they're a few days apart.

@clokep clokep added the X-Needs-Info This issue is blocked awaiting information from the reporter label Feb 1, 2022
@Half-Shot
Copy link
Collaborator Author

It does seem to be very similar, synapse-federation-inbound-0 _process_incoming_pdus_in_room_inner
image

@erikjohnston
Copy link
Member

@Half-Shot if you still have the data can you post screen shots of the per block metrics please? That should narrow down where in the _process_incoming_pdus_in_room_inner code path the CPU and DB is being spent.

@Half-Shot
Copy link
Collaborator Author

Sorry, the data will have evaporated by now :(. I'll catch it next time.

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

No branches or pull requests

3 participants