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

ephermeralForTest engine does not implement getLatestOplogTimestamp

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Steps To Reproduce:
      Hide

      1. Run any suite that uses a sharded cluster with the ephemeralForTest engine.

      Show
      1. Run any suite that uses a sharded cluster with the ephemeralForTest engine.
    • Sprint:
      Sharding 2021-03-08
    • Linked BF Score:
      0

      Description

      After the changes on SERVER-54345 we need to wait for a write to reach majority when creating the shard index before continuing, to prevent that a rollback ends up having a sharded collection without the shard key index on the primary shard. However, the ephemeralForTest engine does not implement getLatestOplogTimestamp, causing a consistent failure when running any sharded test when using that engine. We could use something like waitForWriteConcern to wait for majority.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              marcos.grillo Marcos José Grillo Ramirez
              Reporter:
              marcos.grillo Marcos José Grillo Ramirez
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: