[SERVER-38375] Check for duplicates during hybrid builds while draining Created: 03/Dec/18 Updated: 06/Dec/22 Resolved: 06/May/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Storage Execution
|
||||
| Participants: | |||||
| Description |
|
We currently resolve outstanding duplicate keys at the very end of an index build, at the time of commit, while holding a database X lock. If there a lot of duplicates to resolve under a heavy write workload, it may be advantageous to resolve duplicates at every drain phase "MultiIndexBlock::drainBackgroundWritesIfNeeded()". |
| Comments |
| Comment by Sara Williamson [ 06/May/19 ] |
|
We don't believe this would be a serious performance improvement and we're unsure of its viability; therefore closing as won't fix. |