We got heard by the powers to be at MongoDB and are now working with them to res...

nevi-me · on Oct 1, 2016

I thought you would have reported the issue before/at the same time as the blog post. My opinion's that it sometimes works out better if I get in touch with software developers first, in case there is a known issue and/or workaround.

I say this because most posts about issues we experience don't end up being on HN, and add a result the powers that be either don't hear us, or by the time we've logged issues and gotten the problems resolved; there's no longer enough time to spend another week migrating again to WT.

If the issue isn't resolved by 3.2.10 as mentioned elsewhere, I hope it gets resolved soon so you can get that 7x throughout improvement.

helloanand · on Oct 1, 2016

Yes, we did report the issue to MongoDB. They've acknowledged that the issue does exist, and are working with us to repro/resolve.

juanroy · on Oct 1, 2016

It's sure you will get the most of Wired Tiger storage engine again die to 3.2.10 release!