[SERVER-8505] Document size limit can cause idempotency issues Created: 11/Feb/13 Updated: 21/Sep/17 Resolved: 11/Feb/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Write Ops |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Case: | (copied to CRM) | ||||||||
| Description |
|
Initial document state: {} Oplog entries:
Final state: {a: '', b: '15MB string'}Note that at no point is the document more than 16MB so this is a valid sequence of events from the primary's perspective. If we start applying Oplog entry 1 to the final document (which initial sync assumes is valid) we will have a document temporarily larger than 16MB which will cause an error and abort the server. |
| Comments |
| Comment by Mathias Stearn [ 11/Feb/13 ] |
|
Nope, looks like a dup. Didn't know about the earlier ticket. Good catch. |
| Comment by Aaron Staple [ 11/Feb/13 ] |
|
Closing as a dup, but lmk if I missed anything. |
| Comment by Aaron Staple [ 11/Feb/13 ] |
|
I think this is SERVER-7515. |