Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-27543

Create new metadata for oplog queries



    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Done
    • None
    • 3.4.4, 3.5.4
    • Replication
    • None
    • Fully Compatible
    • v3.4
    • Repl 2017-01-23, Repl 2017-02-13, Repl 2017-03-06
    • 0


      Oplog queries require different metadata from heartbeats. There are fields that each need that the other doesn't, and there are fields that one should consider that the other should not. As we are defining the role that each of these commands play in the replication process, the metadata that each replication command carries must be clarified as well. We will now have ReplSetMetadata with $replData like we have now, but we will add in a new OplogQueryMetadata with $oplogQueryData. The OplogQueryMetadata can have the primaryIndex, the lastOpCommitted, the syncSourceIndex, the lastOpApplied, and the rbid from after the query. The OplogFetcher will then request both types of metadata. For backwards compatibility we need to keep ReplSetMetadata the same as it is now, but in the future (3.8) we can strip it down to term, configVersion, replsetID, and lastOpCommitted (as long as sharding needs it outside of oplog querying), to deduplicate the fields in OplogQueryMetadata only needed for oplog querying. We will keep having the OplogFetcher request both types of metadata since it needs fields from both. We are only removing fields that other commands like heartbeating do not need.


        Issue Links



              judah.schvimer@mongodb.com Judah Schvimer
              spencer@mongodb.com Spencer Brody (Inactive)
              0 Vote for this issue
              5 Start watching this issue