Three weeks ago today, we deployed the new Socorro file system into production. It was the first in in a series of engineered improvements to the Socorro codebase. By “engineered”, I mean that it was the first major improvement to … Continue reading
As the scope and depth of the Socorro/Breakpad project has evolved in the last nine months, the most nonvolatile requirement of the project has been a file system as the initial server side storage for submitted crash dumps. The file … Continue reading
Over the last week, we’ve encountered some problems in our monitor and processor caused by a large number of pending jobs: main monitor thread takes > 1 hr to complete a full scan of pending jobs on disk priority job … Continue reading
The Socorro database, which is the main database for Firefox 3 crashes, will be going through some maintenance upgrades this week. Starting tonight, this means: Report data prior to June 23rd will be temporarily unavailable. New reports will work as … Continue reading
Last Friday we pushed some important updates to Socorro: Bug 426940 – Reduce or eliminate delay in collector to monitor hand-off Bug 426940 – Fix processor handling of error conditions Bug 428300 – status page too slow This means: When … Continue reading
History can tell you that companies don’t disclose crashes in their software. They keep a pretty close eye on what crashes and bugs are disclosed. Mozilla doesn’t. Rather than being the exception, openness is the rule, and that is one … Continue reading
We’ve pushed some important updates in the last couple of days: refactor of processor code, which is 1/3 of the breakpad server architecture update of reporter to allow for instant queuing of requested reports This means: If you submit a … Continue reading
Socorro has had a few improvements over the last week. bsmedberg, ispiked and luser worked hard to bring you: Graphs to show crash population over time Crash reports by operating system Crash reports by build and operating system There are … Continue reading
Last week I learned a few things (the hard way) about PostgreSQL (pgsql) partitioning: You really have to read the “caveats” part of the manual (scroll down, very bottom) Server config matters (SET constraint_exclusion = on;) if you want to … Continue reading
