[SERVER-21985] WiredTiger range scans can see out of order keys Created: 22/Dec/15 Updated: 22/Dec/15 Resolved: 22/Dec/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.2.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Alexander Gorrod | 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: | |||||||||||||
| Description |
|
Under some high update workloads WiredTiger range scans can return keys out of order. This has been seen in cases where oplog iterators report jumps in key range. |