[SERVER-5218] Add a write concern to wait for journal on all 'w' servers Created: 06/Mar/12  Updated: 25/Jan/17  Resolved: 01/May/15

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.1.3

Type: Improvement Priority: Minor - P4
Reporter: Glenn Maynard Assignee: Siyuan Zhou
Resolution: Done Votes: 3
Labels: elections
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-6998 Write concern cannot guarantee journa... Closed
Related
related to SERVER-7156 w:majority issues with votes Closed
related to SERVER-17852 Reduce unnecessary replicated journal... Closed
is related to SERVER-18023 Don't await commit when applying logo... Closed
Tested
Backwards Compatibility: Minor Change
Sprint: RPL 1 04/03/15, RPL 3 05/15/15
Participants:

 Description   

https://groups.google.com/forum/#!topic/mongodb-user/PeJxfoH6RF4

{w: 3, j: true}

should wait for journaling on all waited nodes, in order to permit safe two-phase commit systems, and other high-resilience clients, to be sure that data has actually hit the disk on those replicas. This also seems like the natural behavior for this combination of options: w says how many replicas to wait for, and j says to wait for journalling on those nodes.



 Comments   
Comment by Githook User [ 30/Apr/15 ]

Author:

{u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'siyuan.zhou@mongodb.com'}

Message: SERVER-5218 Batch oplog writes always wait for journal.
Branch: master
https://github.com/mongodb/mongo/commit/673bb299696b4afc16c2e2ebaa9a35600ec2969c

Comment by Githook User [ 30/Apr/15 ]

Author:

{u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'siyuan.zhou@mongodb.com'}

Message: Revert "SERVER-5218 Batch oplog writes always wait for journal."

This reverts commit 27a8cb772d9e876fc7549a2c6ce3c1a62a4a394f.
Branch: master
https://github.com/mongodb/mongo/commit/66a48710fcdfa9783d44f1b467a7bceb6df7dcd2

Comment by Githook User [ 29/Apr/15 ]

Author:

{u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'siyuan.zhou@mongodb.com'}

Message: SERVER-5218 Batch oplog writes always wait for journal.
Branch: master
https://github.com/mongodb/mongo/commit/27a8cb772d9e876fc7549a2c6ce3c1a62a4a394f

Comment by Eric Milkie [ 22/Apr/15 ]

The Election Enhancements project requires that operations are durably written before reporting upstream.
Therefore, we will be making the following changes:
1. When protocolVersion = 1, batch oplog writes will always wait for journal before the reporter reports optime position upstream.
2. We will no longer attach j:true to ops in the oplog.
3. Document that j:true is respected for all w when waiting for write concern, but only for replsets with protocolVersion 1.

Comment by Githook User [ 01/Apr/15 ]

Author:

{u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'siyuan.zhou@mongodb.com'}

Message: SERVER-5218 Replicate journal write concern flag
Branch: master
https://github.com/mongodb/mongo/commit/8f19f04b228b56fd0ae934c3a943192b16225823

Comment by Eliot Horowitz (Inactive) [ 06/Mar/12 ]

I don't think we'll change the behavior of j, but could add a new option.

Generated at Thu Feb 08 03:08:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.