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

Direct config server write in batch_write_command_sharded.js should wait for replication

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor - P4 Minor - P4
    • 3.3.5
    • None
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 13 (04/22/16)
    • 0

    Description

      The batch_write_command_sharded.js has a step, which directly writes to the config servers and then performs operation, which expects the data just written to be visible by mongos. This may not happen if the write has not propagated to the secondary node chosen by mongos.

      We should fix the test to wait for replication.

      Attachments

        Activity

          People

            kaloian.manassiev@mongodb.com Kaloian Manassiev
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: