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

workers are spamming 'restarting logcontext' warnings #7202

Closed
richvdh opened this issue Apr 1, 2020 · 2 comments
Closed

workers are spamming 'restarting logcontext' warnings #7202

richvdh opened this issue Apr 1, 2020 · 2 comments
Assignees
@richvdh

Comments

@richvdh
Copy link
Member

richvdh commented Apr 1, 2020 

2020-04-01 00:09:04,234 - synapse.logging.context - 345 - WARNING - replication-RDATA-events-751607 - Re-starting finished log context replication-RDATA-events-751607

etc.
@richvdh
Copy link
Member Author

richvdh commented Apr 1, 2020

this will have been introduced by #7120, but I think it's pointing to an underlying issue.

@richvdh richvdh self-assigned this Apr 1, 2020
richvdh added a commit that referenced this issue Apr 1, 2020
@richvdh
Remove some run_in_background calls in replication code
5f4d114 
By running this stuff with `run_in_background`, it won't be correctly reported
against the relevant CPU usage stats.

Fixes #7202
@richvdh richvdh mentioned this issue Apr 1, 2020
Merged
richvdh added a commit that referenced this issue Apr 3, 2020
@richvdh
Remove some run_in_background calls in replication code (#7203)
bae3274 
By running this stuff with `run_in_background`, it won't be correctly reported
against the relevant CPU usage stats.

Fixes #7202
@richvdh
Copy link
Member Author

richvdh commented Apr 3, 2020

#7203

@richvdh richvdh closed this as completed Apr 3, 2020
phil-flex pushed a commit to phil-flex/synapse that referenced this issue Jun 16, 2020
@richvdh @phil-flex
Remove some run_in_background calls in replication code (matrix-org…
2c6d729 
…#7203)

By running this stuff with `run_in_background`, it won't be correctly reported
against the relevant CPU usage stats.

Fixes matrix-org#7202
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@richvdh richvdh

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@richvdh