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

OplogFetcher should run LogicalTimeMetadataHook on reply metadata

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.4
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Repl 2020-02-24
    • 21

      Before SERVER-45574, OplogFetcher used RemoteCommandRetryScheduler on the ReplicationExecutor to run oplog fetching queries. And all connections in the executor thread pool run LogicalTimeMetadataHook on incoming command replies to advance the logical clock.
      After SERVER-45574, OplogFetcher uses DBClientConnection and DBClientCursor for oplog fetching. So we should add cluster time metadata handling to the DBClientConnection's metadata reader. Otherwise, the syncing node could advance the commit point (in processMetadata) beyond the logical clock.

            Assignee:
            lingzhi.deng@mongodb.com Lingzhi Deng
            Reporter:
            lingzhi.deng@mongodb.com Lingzhi Deng
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: