[SERVER-18374] Write commands should not wait for replication if no write happened Created: 07/May/15  Updated: 26/Apr/19  Resolved: 22/Jul/15

Status: Closed
Project: Core Server
Component/s: Write Ops
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Andy Schwerin Assignee: Scott Hernandez (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-18522 Majority (WC) writes, even no-ops, mu... Closed
Backwards Compatibility: Minor Change
Operating System: ALL
Participants:

 Description   

If a write command, say an update, doesn't result in any actual writes (i.e., nModified is 0 on an update), no new oplog entry is recorded, so it's not meaningful to wait for that operation to replicate. As such, write commands should never wait for replication if they have done no writes.



 Comments   
Comment by Ian Whalen (Inactive) [ 26/Apr/19 ]

Switching "Drivers Changes Needed" from "Maybe" to "Not Needed" since this was closed as something other than Fixed.

Comment by Scott Hernandez (Inactive) [ 22/Jul/15 ]

SERVER-18522 only applies to w>= majority, correct? This would apply to any w<majority. We might want to be clear that we don't intend to support this behavior, if that is what you meant.

Comment by Andy Schwerin [ 22/Jul/15 ]

This is essentially the opposite of SERVER-18522.

Comment by Scott Hernandez (Inactive) [ 07/May/15 ]

And they are wrong, but I'll have more.

Comment by Eric Milkie [ 07/May/15 ]

Scott already has some ideas for this.

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