Closed Bug 930783 Opened 11 years ago Closed 11 years ago

please deploy browserid train-2013.10.23 to stage

Categories

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

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: jhirsch, Assigned: gene)

References

Details

Assignee: nobody → jrgm
Assignee: jrgm → kthiessen
we're planning on pushing to stage on 10/28
Blocks: 932041
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: kthiessen → gene
Looks like this new build has a new config setting that convict is choking on : @40000000527c1364182999ac UNCLE: Error: max_compute_processes: must be an integer @40000000527c13641829a564 at Object.rv.validate (/opt/browserid/node_modules/convict/lib/convict.js:377:15) @40000000527c13641829ad34 at Object.<anonymous> (/opt/browserid/lib/configuration.js:498:6) @40000000527c13641829b11c at Module._compile (module.js:449:26) @40000000527c13641829b8ec at Object.Module._extensions..js (module.js:467:10) @40000000527c13641829c0bc at Module.load (module.js:356:32) @40000000527c13641829c4a4 at Function.Module._load (module.js:312:12) @40000000527c1364182aab1c at Module.require (module.js:362:17) @40000000527c1364182ab2ec at require (module.js:378:17) @40000000527c1364182ab6d4 at Object.<anonymous> (/opt/browserid/lib/logging/transports/log-file.js:13:23) @40000000527c1364182abea4 at Module._compile (module.js:449:26) What is this new config setting? What kind of value should it have? Any other new config values?
Flags: needinfo?(jhirsch)
QA Contact: kthiessen
Flags: needinfo?(jhirsch) → needinfo?(kthiessen)
Flags: needinfo?(jhirsch)
Ermahgawd, so sorry. Yes, there's a little bit adjustment to config. max_compute_process used to take `null` to mean use default, now it takes 0 to use the sane default. (Or you could just leave it out if you wanted, and the default will be using from lib/configuration.js, which is 0 already. Also, all kpi_* config properties became kpi.*. So, they're now something like: kpi: { backend_sample_rate: 0.2 // i dunno! }
Flags: needinfo?(jhirsch)
Ok, I've made these config changes here : https://github.com/mozilla/identity-ops/commit/4a186cc79dd2a530ebd0fcf7f51aba977d0a176d and will build new AMIs and staging stack
Flags: needinfo?(kthiessen)
Stack 1108 has been built and staging DNS pointed to it.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
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).
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Blocks: 939961
I'll spin up a staging and 2 prod stacks of this by Wednesday morning. Apologies for the delay, I'm working on fxa
Stack 1211 is up and DNS has been pointed to it in stage.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
Old deployment -- belatedly marking VERIFIED.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.