Configure zero-downtime deployments #198
Labels
No Label
Priority
Critical
Priority
High
Priority
Low
Priority
Normal
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Type
Breaking
Type
Documentation
Type
Enhancement
Type
Feature
Type
Report
Type
Security
Type
Suggestion
Type
Testing
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: infrastructure/extensions-website#198
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Now that we get some sustained traffic, it would be good avoid dropping requests due to uwsgi restart during deploys (502 error).
Relying on systemd-managed socket, we should be able to do this with minimal changes to our uwsgi setup.We should use reload instead of restart: https://uwsgi-docs.readthedocs.io/en/latest/articles/TheArtOfGracefulReloading.html#standard-default-boring-graceful-reload-aka-sighup
Testing on staging:
brings the service down
to fix:
UPD: this is no longer relevant, socket unit is not needed
this approach didn't solve the problem of in-flight requests being killed during restart
Fixed in
d3a48372b4