[SERVER-38989] Update serverStatus.opcountersRepl.command on secondaries for atomic applyOps Command. Created: 14/Jan/19 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: | Suganthi Mani | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Replication
|
||||
| Backport Requested: |
v4.0
|
||||
| Participants: | |||||
| Description |
|
On primary we update both the command counter and also CRUD ops counters for atomic applyOps command. But, on secondaries, during oplog application, we apply only the CRUD ops counter and not the command counter accounting for applyOps command. 3.6 will be incrementing command and CRUD ops counter for applOps cmd due to this BACKPORT-3609. And they don't decompose the applyOps command operation during secondary oplog application as we do it from 4.0 version onwards.
|