Breakpad/Status Meetings/2015-02-04: Difference between revisions
< Breakpad | Status Meetings
Jump to navigation
Jump to search
(→ES: es9 fail) |
(→Other: pg/duplicates/api) |
||
Line 37: | Line 37: | ||
=== Other === | === Other === | ||
Postgres module related: | |||
* Just added all SQL files to our package distro | |||
Duplicate detection: | |||
* Lars added md5sum to the collector, so we are on our way to deprecating the reports_duplicates process inside Postgres (yay) | |||
API: | |||
* ProductVersions is next up for API migration, had paused to work on deprecating product_info, but it is taking too long so selena is going to migrate this as-is and refactor/deprecate some junk related to this later | |||
* Saw a possible request for ADI API endpoint - any special concerns, or can I make this using existing whitelist/blocklist API features? | |||
=== PR Triage === | === PR Triage === |
Revision as of 18:00, 4 February 2015
« previous meeting — index – next week » create?
Meeting Info
Breakpad status meetings occur on Wed at 11:00am Pacific Time.
Conference numbers:
Vidyo: Stability 650-903-0800 x92 conf 98200# 800-707-2533 (pin 369) conf 98200#
IRC backchannel: #breakpad
Mountain View: Dancing Baby (3rd floor)
Operations Updates
AWS
- getting close on symbol migration
- NFS symbol store synchronized to S3, few minutes lag or less
- currently-open PR to make processor use symbols in S3
- https://github.com/mozilla/socorro/pull/2614
- once this lands we can switch stage/prod to S3 symbol store
- there are a few microservices that use symbol store:
- MS-style symbol server symbols.m.o in heroku
- symbolapi.m.o (aka snappy symbolication service) waiting for EC2 node
- too CPU intensive to run on Heroku unless we use the (expensive!) dynos
DB
ES
- es9 had a disk and/or controller failure and has been removed from the cluster. See bug 1129487 for more info.
Other
Postgres module related:
- Just added all SQL files to our package distro
Duplicate detection:
- Lars added md5sum to the collector, so we are on our way to deprecating the reports_duplicates process inside Postgres (yay)
API:
- ProductVersions is next up for API migration, had paused to work on deprecating product_info, but it is taking too long so selena is going to migrate this as-is and refactor/deprecate some junk related to this later
- Saw a possible request for ADI API endpoint - any special concerns, or can I make this using existing whitelist/blocklist API features?