[SERVER-12012] apply semantic write concern checks before writes applied Created: 09/Dec/13 Updated: 10/Dec/14 Resolved: 08/Jan/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Greg Studer |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
For batch writes, it is important that expected write concern checks that are not write concern failures happen before writes are sent. For example, j : true with journaling off is disallowed, but is enforced after writes have already been processed. |
| Comments |
| Comment by Daniel Pasette (Inactive) [ 08/Jan/14 ] |
|
duplicate: |