[SERVER-85734] Include record size in size limit tracker for extra key check Created: 25/Jan/24 Updated: 31/Jan/24 Resolved: 31/Jan/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Xuerui Fa | Assignee: | Backlog - Replication Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | pm-855-milestone-5 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Replication
|
||||||||
| Participants: | |||||||||
| Description |
|
Today, it seems we do not include the record size as part of tracking how many bytes dbCheck has seen so far. The record should be fairly large, so we should include it when determining when to stop dbCheck due to size limitations, and when to throttle the speed of dbCheck. |