-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Release Synapse v1.45.0 #11058
Comments
We released v1.45.0rc1 earlier today: https://github.com/matrix-org/synapse/releases/tag/v1.45.0rc1 Because of a time constraint on getting the RC out, not all the release blockers were fixed, see
X-Release-Blocker
The intention is for @DMRobertson (as the maintainer for this week) to release a v1.45.0rc2 (hopefully) later this week with these fixes, before we release v1.45.0. |
#11053 is deployed to matrix.org with 27e6e45 Grafana shows that the user directory worker isn't stuck on CPU: I don't like the climbing memory usage there before my change. I'm guessing that the background process constantly failing means that something wasn't getting GCed? Here's a view of the last half an hour where you can see the restart. I was hoping to see forward progress recorded in the DB too, but for now it's consistently saying
Which I don't find too reassuring. |
As soon as I asked @erikjohnston to take a look, the issue resolved itself. Here's that graph again: We observed:
We concluded that all is fine now, even if it is a little concerning. |
v1.45.0rc2 was released today: https://github.com/matrix-org/synapse/releases/tag/v1.45.0rc2 It contains the fix to the user directory issue, but not the one to the performance issue. @DMRobertson what's the plan here? Is the performance issue still a release blocker, and we should release an rc3 tomorrow or on Monday? |
I'm not sure. I don't yet understand what the underlying cause of the issue (issues?) is. Was hoping to talk it over in the backend triage meeting this afternoon. One person changed their configuration to use workers and they report that the lockups have stopped. The other r[eported that turning presence off reduced the impact of their mass DNS lookups] (#11049 (comment)), by a factor of two.
I think we should if we have a proposed fix. |
After discussion in the planning meeting, we decided that #11049 was no longer a release blocker. I've asked the reporters to confirm that this was a regression by rolling back. If so, we may ask them to git bisect to figure out what introduces the problem. |
Release completed. https://github.com/matrix-org/synapse/releases/tag/v1.45.0 |
We're going to do a 1.45.1 release to roll back #10947 temporarily |
This issue tracks the progress of the v1.45.0 release of Synapse, which is due to be released on October 19th.
The text was updated successfully, but these errors were encountered: