[SERVER-16777] Capped collection truncation behavior across storage engines is inconsistent Created: 08/Jan/15 Updated: 15/Jan/15 Resolved: 13/Jan/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 2.8.0-rc4 |
| Fix Version/s: | 2.8.0-rc5 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jonathan Balsano | Assignee: | Jonathan Balsano |
| Resolution: | Done | Votes: | 0 |
| Labels: | 28qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
Looking at these two lines of source in WT and MMapV1: WT: https://github.com/mongodb/mongo/blob/r2.8.0-rc4/src/mongo/db/storage/wiredtiger/wiredtiger_record_store.cpp#L353 Note that in WT a '>' is used and in MMapV1 a '>=' is used. Given a capped collection of size 100, if we insert two documents of size 50 and then truncation occurs:
These two behaviors should be made the same, likely in favor of the existing MMapV1 behavior. |
| Comments |
| Comment by Githook User [ 10/Jan/15 ] |
|
Author: {u'username': u'jrbalsano', u'name': u'Jonathan Balsano', u'email': u'jonathan.balsano@10gen.com'}Message: Closes #904 Signed-off-by: Benety Goh <benety@mongodb.com> |