Announcing MongoDB 3.0 and Bug Hunt Winners

MongoDB

Releases
Facebook ShareLinkedin ShareReddit ShareTwitter Share

Today MongoDB 3.0 is generally available; you can download now.

Our community was critical to ensuring the quality of the release. Thank you to everyone who participated in our 3.0 Bug Hunt. From the submissions, we’ve selected winners based on the user impact and severity of the bugs found.

First Prize

Mark Callaghan, Member of Technical Staff, Facebook
During the 3.0 release cycle, Mark submitted 10 bug reports and collaborated closely with the MongoDB engineering team to debug the issues he uncovered. As a first place winner, Mark will receive a free pass to MongoDB World in New York City on June 1-2, including a front row seat to the keynote sessions. Mark was also eligible to receive a $1,000 Amazon gift card but opted to donate the award to a charity. We are donating $1,000 to CodeStarters.org in his name.

Honorable Mentions

Nick Judson, Conevity
Nick submitted SERVER-17299, uncovering excessive memory allocation on Windows when using “snappy” compression in WiredTiger.

Koshelyaev Konstantin, RTEC
Koshelyaev submitted SERVER-16664, which uncovered a memory overflow in WiredTiger when using “zlib” compression.

Tim Callaghan, Crunchtime!
In submitting SERVER-16867, Tim found an uncaught WriteConflict exception affecting replicated writes during insert-heavy workloads.

Nathan Arthur, PreEmptive Solutions
Nathan submitted SERVER-16724, which found an issue with how collection metadata is persisted.

Thijs Cadier, AppSignal
Thijs submitted SERVER-16197, which revealed a bug in the build system interaction with the new MongoDB tools.

Nick, Koshelyaev, Tim, Nathan, and Thijs will also receive tickets to MongoDB World in New York City on June 1-2 (with reserved front-row seat for keynote sessions), $250 Amazon Gift Cards, and MongoDB t-shirts.

Congratulations to the winners and thanks to everyone who downloaded, tested and gave feedback on the release candidates.

To learn more about MongoDB 3.0: