-
Type: Improvement
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Index Maintenance
-
Labels:None
-
Storage Execution
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()".