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

stale_mongos_updates_and_removes.js can fail because data isn't replicated fast enough

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.3.5
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Sharding 13 (04/22/16)
    • Linked BF Score:
      0

      Description

      stale_mongos_updates_and_removes.js uses two mongos, setting one up as stale before testing operation correctness. During setup, however, the moveChunk call on the second mongos to make the first stale fails because shardCollection was executed on the first and the second runs into a collection not sharded error. So need to add an awaitReplication on the config replset before making the first mongos stale.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: