[SERVER-21530] inMemory storage engine should report the capped size as storage size Created: 18/Nov/15 Updated: 17/Apr/16 Resolved: 11/Dec/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 3.2.0-rc3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Charlie Swanson |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL | ||||||||||||
| Steps To Reproduce: | apply this diff:
then run
|
||||||||||||
| Participants: |
| Description |
|
The inMemory storage engine reports the storage size to be equivalent to the data size. This causes the convert_to_capped_collection fsm workload to fail, because it expects the storage size to be the capped size, which should be rounded up to a multiple of 256. |
| Comments |
| Comment by Charlie Swanson [ 11/Dec/15 ] |
|
Decided to fix the test to use the max size of the capped collection, instead of the storage size. |
| Comment by Githook User [ 19/Nov/15 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}Message: Similarly for the index and record store. |
| Comment by Githook User [ 19/Nov/15 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}Message: |