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

mongofiles sharded cluster write concern test regression in MongoDB 3.7

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.6.6, 4.1.1
    • Component/s: Sharding
    • Labels:
      None
    • Environment:
      Ubuntu 14.04
    • Sharding
    • ALL
    • Sharding 2018-07-16

      Recent tools Evergreen tests have started showing a failure in the mongofiles_write_concern_mongos.js test when run against a 3.7 nightly. Nothing relating to mongofiles changed in the tools during the time the failures started and the tests pass when run against MongoDB 3.6.

      The test case has 2 nodes of a 3-node shard down, but mongofiles is run with w:1,wtimeout:10000. In the failing case, mongofiles hangs waiting for a database response. Eventually, after several hours, the process is terminated.

      Note: The mongofiles log output is deceptive, it claims the file is added, but the hang occurs during a deferred close() call when mgo is trying to flush all data to the database and ensure indexes exist.

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            david.golden@mongodb.com David Golden
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: