MongoRocks Deprecated for MongoDB 3.6?

[Mark G.]

Hi all,

Just curious if anyone has any insight on why the storage engine that Percona was pushing as a replacement for a previously deprecated engine - PerconaFT - is now itself going away. Did the 3.6 base change so much that RocksBD is no longer a viable storage engine? I haven't seen nor heard anything that would necessitate this, but I might not have looked in the right places. Kinda makes me wonder what else is on the chopping block.

--Mark

[Mark G.]

Well, there is now a blog post that explains it: https://www.percona.com/blog/2018/05/10/why-weve-deprecated-mongorocks-in-percona-server-for-mongodb-3-6/

[Chan Lewis]

That's really a pity. According to its saying, there're plenty of new features introduced from mongo 3.6&4.x， however do it mean there will be plenty of changes on storage engine itself ?  

[Justin Swanhart]

Yes, as explained in the blog post, many changes were made to the storage layer to integrate these new features for WiredTiger, and it would require substantial effort to update the Rocks engine interface to support those features, and there is little commercial interest for the Rocks layer, and updating it is not commercially viable as a result.

--Justin

--
You received this message because you are subscribed to the Google Groups "Percona Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to percona-discuss...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/percona-discussion/71c065da-99df-4e24-a01d-6fb2df743bbbn%40googlegroups.com.