[SERVER-1375] does repairDatabase overpack? Created: 07/Jul/10 Updated: 06/Dec/22 Resolved: 15/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Trivial - P5 |
| Reporter: | Dwight Merriman | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Operating System: | ALL |
| Participants: |
| Description |
|
Normally we use a paddingFactor to determine how much padding to put at the end of records. This way there is not too much movement on small additions to a record, and the factor is adaptive. However I am wondering if during a repair (or any clone including initial sync of a replica slave) if it looks like all inserts, and thus the factor is too low. Everything gets packed in tightly which isn't correct. One way to fix is to use the old paddingfactor if it is reasonable as a hint. |