[SERVER-11989] fail points for batch write in mongod Created: 06/Dec/13 Updated: 10/Dec/14 Resolved: 25/Feb/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Greg Studer |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
It would be useful for testing to have one or two fail points in mongod which could simulate different kinds of batch errors:
|
| Comments |
| Comment by Bernie Hackett [ 21/Feb/14 ] |
|
I'm fine with closing this. |
| Comment by Greg Studer [ 19/Feb/14 ] |
|
jeff.yemin behackett - This ticket was opened when we had a different/more complex output format for batch writes - with the new behavior it seems pretty simple to trigger failures in the middle of a batch (update with $invalid operator), invalid write concern errors (j:true,fsync:true) and regular write concern failures (w:"invalid"). Are there any areas in particular that you think still need attention? |