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

safe_secondary_reads_causal_consistency.js must wait for effects of _configsvrCommitChunkMigration to be majority-committed snapshot on all CSRS members

    • Fully Compatible
    • v4.7, v4.4, v4.2
    • Sharding 2020-09-21, Sharding 2020-10-05
    • 0

      The safe_secondary_reads_causal_consistency.js test waits for the hangBeforePostMigrationCommitRefresh failpoint to be hit on the donor shard. This only ensures the donor shard has run the _configsvrCommitChunkMigration command against the config server primary and doesn't guarantee the effects of the _configsvrCommitChunkMigration command are visible on all CSRS members. The router may refresh from a node other than the CSRS primary and not see the effects of the _configsvrCommitChunkMigration command.

      st.configRS.awaitLastOpCommitted();
      

      prior to running the flushRouterConfig command would ensure the mongos0 process fetches the latest version of the routing table and will always attempt to route the _id:2 insert to shard1.

            Assignee:
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Reporter:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: