Closed Bug 939961 Opened 11 years ago Closed 11 years ago

please deploy browserid train-2013.10.23 to production

Categories

(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 958719

People

(Reporter: kthiessen, Assigned: gene)

References

Details

from bug 930783: sha: fdfdd553fa3c2a417c80d7457ced984a05fb9120 ChangeLog: https://github.com/mozilla/browserid/blob/train-2013.10.23/ChangeLog#L2-L11 Schedule: http://personatra.in/#2013.10.23 RPM now on r6: /home/kthiessen/Library/github/mozilla/browserid_private/ rpmbuild/RPMS/x86_64/browserid-server-0.2013.10.23-1.el6_122101.x86_64.rpm (with no line-break in the path)
Assignee: nobody → gene
QA Contact: kthiessen
Stacks 1119 built at both us-west-2 and us-east-1 in production. When would you like to plan to switch traffic to these?
Flags: needinfo?(kthiessen)
:jrgm is running load tests on staging today/tomorrow morning. After we've had a chance to check those results and do a quick overall sanity check, I'd like to switch prod. I'd say some time between 2 and 3 tomorrow (Tue) afternoon, if that works ok for you.
Flags: needinfo?(kthiessen)
Sounds good
This is going to be delayed due to problems found by :jrgm with the load tests. Details to follow in email from :jrgm.
There's not a great bit of detail to follow. Basically, the toobusy stuff, which never fires during a 250K ADU load test, instead was firing about 100 times per hour (i.e., something was stalling the event loop for >40 ms).
this bug hasn't moved in a couple of days. is anyone working on reproducing the load test errors or finding the offending changes via git bisect?
This deployment is blocked by https://github.com/mozilla/persona/issues/4027 -- see that issue for details.
We haven't found a definitive resolution to the 'too busy' problem, and this is increasingly looking like it is a problem with AWS. So I put in a pull request to increase maximum_event_loop_lag to 100ms. Gene: could you build a new stage stack with this change https://github.com/mozilla/identity-ops/pull/138 (and keeping the same rpm for train-2013.10.23).
Hmm, I now see this is the production deploy ticket. Nevermind.
Depends on: 930783
With this train going live in stage last week, when should I plan to put this into production?
Flags: needinfo?(kthiessen)
Yeah Gene, if you could build production stacks for this train, that would be good, and if we can find a time that works we can ship this week.
Seconding :jrgm's comments -- he's got as much context here as I do.
Flags: needinfo?(kthiessen)
Stack 1217 is up in both datacenters
Fuck it. This rpm does not have this commit - https://github.com/mozilla/persona/pull/4035. Closing this bug.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INCOMPLETE
This train is derailed. Merry Christmas.
Ok, I'll tear down those prod stacks
Resolution: INCOMPLETE → FIXED
Talked to jrgm and karl. We're going to work on hot patching still but heavily considering waiting till 2014 for deploy to reduce any risk over the holiday break. We'll revisit this tomorrow to see where we're at.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Marking as dupe to forward people to the new production ticket.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.