[SERVER-16006] write conflict on single-update isn't being retried Created: 06/Nov/14 Updated: 10/Dec/14 Resolved: 07/Nov/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 2.8.0-rc0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Percy | Assignee: | Kaloian Manassiev |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | 28qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
|||||||||||||||||||||||
| Operating System: | ALL | |||||||||||||||||||||||
| Steps To Reproduce: | repro script / jstest that runs two threads that update the same document:
|
|||||||||||||||||||||||
| Participants: | ||||||||||||||||||||||||
| Description |
|
When using WiredTiger, if a WriteConflictException happens with a single update, the operation returns nModified: 0 to the client, and the document is not updated. |