WiredTiger support?

[rocksfrow]

@nicktacular I was curious if you've done any testing on mongodb 3.0 using the new wiredtiger storage engine?

I plan to do the drop-in upgrade from 2.6 to 3.0 on my testbed and I will confirm that drop-in replacement works fine (I don't expect any issues).

BUT, I am definitely going to do more testing once switching out the storage engine.

3.0 boasts up to 10x performance -- while using 80% less disk space.

http://docs.mongodb.org/manual/release-notes/3.0-upgrade/

[rocksfrow]

FYI - switching to WiredTiger is a diff process than the normal upgrade.

I don't expect any issues but I wanted to open this issue as a reference to get some feedback from others / if others have upgraded yet.

http://docs.mongodb.org/manual/release-notes/3.0-upgrade/#upgrade-repl-set-wiredtiger

[rocksfrow]

@nicktacular any thoughts on this? You might be able to shrink your cluster size after making this upgrade ;)

[nicktacular]

Hey @rocksfrow haven't had a chance to work on this yet. I'm unable to do any work on this for the moment and will have to postpone for a few months at this point.

[rocksfrow]

Nick,

Thanks for letting me know. I will be testing with wired tiger later this
week and will let you know how it goes.

btw, have you thought of using the ttl on the session collection to avoid
the need for the cleanup method? IE just set the ttl of the record to
session expire time and Mongo will auto purge (as of 2.2).

Also, are you using sharing or just replica?

Note, this email was sent from my cell phone.

Hey @rocksfrow https://github.com/rocksfrow haven't had a chance to work
on this yet. I'm unable to do any work on this for the moment and will have
to postpone for a few months at this point.

—
Reply to this email directly or view it on GitHub
#23 (comment)
.