[SERVER-27668] Remove unnecessary fields in ReplSetMetadata Created: 12/Jan/17 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | former-quick-wins | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
|
| Comments |
| Comment by Vesselina Ratcheva (Inactive) [ 06/Aug/20 ] |
|
PM-1791 requires the lastOpVisible to stay in ReplSetMetadata. The cloners will cache this every batch so that we know how much oplog we need to apply to be consistent. |
| Comment by A. Jesse Jiryu Davis [ 25/Mar/20 ] |
|
We do now process OplogQueryMetadata in OplogFetcher. The rest of this ticket is still incomplete. |
| Comment by Jason Chan [ 05/Aug/19 ] |
|
We shouldn't remove lastopCommitted from ReplSetMetadata since as of v4.2, the last committed wall time is required. |
| Comment by Spencer Brody (Inactive) [ 14/Feb/17 ] |
|
Moving this into Needs Triage until we can move it into a bucket for work for 3.8 |
| Comment by Judah Schvimer [ 01/Feb/17 ] |
|
lastOpCommitted may need to stay in the ReplSetMetadata for now since it's used to update the commit point on arbiters, and is used in sharding. |
| Comment by Spencer Brody (Inactive) [ 13/Jan/17 ] |
|
We'll need to be processing the OplogQueryMetadata in the OplogFetcher in 3.6 so that when 3.8 stops sending those fields in the ReplSetMetadata we don't break mixed 3.6-3.8 operation. |