Comments on: Exciting Pre-Cursors to MongoDB 3.6 Transactions https://www.percona.com/blog/mongodb-3-6-transactions/ Tue, 06 Aug 2019 20:01:20 +0000 hourly 1 https://wordpress.org/?v=6.5.2 By: Tom Blamer https://www.percona.com/blog/mongodb-3-6-transactions/#comment-10968803 Fri, 15 Dec 2017 16:51:33 +0000 https://www.percona.com/blog/?p=46425#comment-10968803 Thanks for the clarification re: writeConcernMajorityJournalDefault.

]]> By: Adamo Tonete https://www.percona.com/blog/mongodb-3-6-transactions/#comment-10968802 Fri, 15 Dec 2017 11:51:05 +0000 https://www.percona.com/blog/?p=46425#comment-10968802 Thank you for reporting that John!

]]> By: Adamo Tonete https://www.percona.com/blog/mongodb-3-6-transactions/#comment-10968801 Fri, 15 Dec 2017 11:48:07 +0000 https://www.percona.com/blog/?p=46425#comment-10968801 Hi Tom, I could understand your confusion however with protocolVersion:1 majority is assumed. As such it could be a majority setting in 3.4, or be more forced in 3.6 with the forced move to this new protocol. You can read more about that @ https://docs.mongodb.com/v3.4/reference/replica-configuration/#rsconf.writeConcernMajorityJournalDefault

]]> By: John Page https://www.percona.com/blog/mongodb-3-6-transactions/#comment-10968800 Fri, 15 Dec 2017 09:28:04 +0000 https://www.percona.com/blog/?p=46425#comment-10968800 FYI – it’s Causal consistency not casual consistency 🙂

]]> By: Tom Blamer https://www.percona.com/blog/mongodb-3-6-transactions/#comment-10968788 Wed, 13 Dec 2017 23:06:32 +0000 https://www.percona.com/blog/?p=46425#comment-10968788 > This new version gossips the cluster time to each other and keeps this internal clock from trusting the machine’s clock. It means it is virtually impossible to go back in time, as all the operations occur sequentially unless you aren’t writing with w:majority (which is now the default).

Hi Adamo, I checked the 3.6 release notes and I do not see anything about the default write concern changing. Did you mean to say read concern?

]]>