[SERVER-41293] Metadata size is double counted in Document::getApproximateSize() Created: 23/May/19 Updated: 29/Oct/23 Resolved: 30/May/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.14 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ian Boros | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Query 2019-06-03 |
| Participants: |
| Description |
|
We compute the size used in DocumentStorage here and then again here. The second time, we call getApproximateSize() on the geoNearPoint and searchHighlight metadata fields. We should change getApproximateSize() to still count the approximate size of geoNearPoint and searchHighlight, but not to double count the space metadata fields use in DocumentStorage.
As part of this work, we may be able to revert the "allowDiskUse: true" added in this line as part of |
| Comments |
| Comment by Githook User [ 30/May/19 ] |
|
Author: {'name': 'Martin Neupauer', 'email': 'martin.neupauer@mongodb.com', 'username': 'MartinNeupauer'}Message: |