[SERVER-38500] Modularize index constraint violations checking into an independent action Created: 10/Dec/18 Updated: 06/Dec/22 Resolved: 04/Jan/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | 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 | ||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
Constraint checking must be separated from finishing the building phase of an index. Separate function calls on the MultiIndexBlock (index builder). Simultaneous index builds on secondaries cannot proceed with constraint violations checking until signaled to do so by the primary. Secondaries should therefore be able to finish building the index itself (scanning, writing), and then at a later point in time perform the constraint violation checks. |
| Comments |
| Comment by Daniel Gottlieb (Inactive) [ 04/Jan/19 ] |
|
milkie correct me if I'm wrong, but I believe due to the complexity of having secondaries double-check index constraints at index build completion time, we've gone back to relying on primaries to correctly perform constraint checking and correctly replicate data. FWIW, the method to do the checking is already separate. I believe this ticket just wants to make it public. That should be easily achievable if the need arises in the future. |