Posts Tagged ‘Socorro’
The future of crash reporting
In recent blog posts I've talked about our plans for Socorro and our move to HBase. Today, I'd like to invite community feedback on the draft of our plans for Socorro 2.0. In summary, we have been moving our data into HBase, the Hadoop database. In 1.7 we began exclusively using HBase for crash storage. In 1.8 we will move the processors and minidump_stackwalk to Hadoop. Here comes the future In 1.9, we will enable pulling data from HBase for the webapp via a web services layer. This layer is also known as "the pythonic middleware layer". (Nominations for ... Read More »
Moving Socorro to HBase
We've been incredibly busy over on the Socorro project, and I have been remiss in blogging. Over the next week or so I'll be catching up on what we've been doing in a series of blog posts. If you're not familiar with Socorro, it is the crash reporting system that catches, processes, and presents crash data for Firefox, Thunderbird, Fennec, Camino, and Seamonkey. You can see the output of the system at http://crash-stats.mozilla.com. The project's code is also being used by people outside Mozilla: most recently Vigil Games are using it to catch ... Read More »
Socorro: Mozilla’s Crash Reporting System
Recently, we've been working on planning out the future of Socorro. If you're not familiar with it, Socorro is Mozilla's crash reporting system. You may have noticed that Firefox has become a lot less crashy recently - we've seen a 40% improvement over the last five months. The data from crash reports enables our engineers to find, diagnose, and fix the most common crashes, so crash reporting is critical to these improvements. We receive on our peak day each week 2.5 million crash reports, and process 15% of those, for a total of 50 GB. In ... Read More »
Socorro Moves to New Hardware
What has two quad core 3GHz 64bit CPUs, sixteen gigs of RAM and makes the Socorro users happy? That would be the new hardware that the Socorro system moved to during a six hour operation on Thursday night. The new hardware was recommended by the folks from the aptly named PostgreSQL Experts, Inc after an intense week of consultation and analysis in March earlier this year. After auditing our existing system of hardware and software, it was apparent that we were woefully underpowered for what we were trying to do. While simply tuning PostgreSQL helped ... Read More »
