[SERVER-68948] Use type 'c' oplog entry for index catalog updates Created: 18/Aug/22 Updated: 08/Sep/22 Resolved: 08/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Marcos José Grillo Ramirez | Assignee: | Marcos José Grillo Ramirez |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | PM-2583-Milestone-1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Sharding EMEA 2022-09-05, Sharding EMEA 2022-09-19 | ||||||||
| Participants: | |||||||||
| Description |
|
Instead of using the observers as they are right now, use a single type c oplog entry to tell secondaries about the index catalog change. This implies preventing writes on config.shard.indexes and config.shard.collections to be replicated, and leverage on the oplog machinery. |
| Comments |
| Comment by Marcos José Grillo Ramirez [ 08/Sep/22 ] |
|
Closing this ticket because the code was merged into SERVER-67123. |