[SERVER-18522] Majority (WC) writes, even no-ops, must enforce replication WC Created: 18/May/15  Updated: 19/Sep/15  Resolved: 04/Aug/15

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

Type: Improvement Priority: Major - P3
Reporter: Scott Hernandez (Inactive) Assignee: Eric Milkie
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-18525 Implement Distributed Lock Manager fo... Closed
Duplicate
is duplicated by SERVER-17744 Enable useful write concern for no-op... Closed
is duplicated by SERVER-14063 Add update no-op mod which replicates Closed
Related
is related to SERVER-18374 Write commands should not wait for re... Closed
Backwards Compatibility: Fully Compatible
Sprint: RPL 7 08/10/15
Participants:

 Description   

On the server enforcing the write concern, the primary replica member, if no write is done then it should enforce a majority write concern on the latest system write.

This is needed so the client can then read the post-state of that write, or something newer. It is especially important if a client needs to retry a write due to a network interruption waiting for the response – if the client then retries the operation, it will look like a no-op to the server, but the write concern still needs to wait until the original write has replicated appropriately.



 Comments   
Comment by Githook User [ 04/Aug/15 ]

Author:

{u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-18522 Ensure replCoord last optime always represents an op that hasn't rolled back
Branch: master
https://github.com/mongodb/mongo/commit/cbfd06f789a99ab446da4f388f018c17225e02d2

Comment by Githook User [ 30/Jul/15 ]

Author:

{u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-18522 permit replicated writes with deleteObjects() (used by sharding)
Branch: master
https://github.com/mongodb/mongo/commit/20e224e7731a0670e813de3c2e67c53328ecc5fa

Comment by Githook User [ 29/Jul/15 ]

Author:

{u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-18522 always update replcoord optime, regardless of operation rollback
Branch: master
https://github.com/mongodb/mongo/commit/6e6435e556a09e1f1a7a565c45f1240a80aa0942

Comment by Githook User [ 29/Jul/15 ]

Author:

{u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-18522 set lastOp to last system optime, on no-op updates or deletes
Branch: master
https://github.com/mongodb/mongo/commit/9ab26585bd47f189c9c6359ad295e3d6e7a03c0c

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