[SERVER-37037] Skip oplog construction in OpObserver on secondaries Created: 06/Sep/18 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Siyuan Zhou | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | former-quick-wins | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Participants: |
| Description |
|
We don't need to generate and write oplog entries in OpObserver on secondaries since the secondaries already copied them form the sync source. The check is at a low level right before writing the oplog entry to the disk. We can skip constructing oplog entries earlier for better performance. |