Closed
Bug 964766
Opened 10 years ago
Closed 7 years ago
Determine how to more gently rev new versions to cause no interruptions
Categories
(Webmaker Graveyard :: DevOps, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: johns, Assigned: johns)
Details
(Whiteboard: [workweek] [devops][workweek-devops] )
Today, we update live on production. This can cause up to a few seconds of a node being unresponsive, causing potential issues for an end user who happens to be on that node at the time. This is less impactful at lower scale, but as we move to scale, this will impact more individuals. We're thinking about how we can safely rev versions without any interruption at all.
Updated•10 years ago
|
Whiteboard: [workweek-devops]
Updated•10 years ago
|
Whiteboard: [workweek-devops] → [workweek] [devops]
Updated•10 years ago
|
Whiteboard: [workweek] [devops] → [workweek] [devops][workweek-devops]
Assignee | ||
Comment 1•10 years ago
|
||
An option I just read about: http://blog.opbeat.com/2014/02/10/makeing-elb-play-nicely-with-django-uwsgi/
Updated•10 years ago
|
Assignee: nobody → johns
Status: NEW → ASSIGNED
Comment 2•7 years ago
|
||
Closing this out as we move to deprecate the Webmaker Component. Issues can be re-filed at https://github.com/mozillafoundation/mofo-devops/issues/new if required.
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•