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

mongofiles sharded cluster write concern test regression in MongoDB 3.7

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Duplicate
    • 3.6.6, 4.1.1
    • None
    • Sharding
    • None
    • Ubuntu 14.04
    • Sharding
    • ALL
    • Sharding 2018-07-16

    Description

      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.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. SERVER-35092 ShardServerCatalogCacheLoader should have a timeout waiting for read concern

          • Major - P3 - Major loss of function.
          • Closed
          is depended on by

          Bug - A problem which impairs or prevents the functions of the product. TOOLS-2035 mongofiles_write_concern_mongos.js fails on server unstable

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-34776 dropDatabase should respect user provided writeConcern

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-34370 Change commands to use AutoGetDb to get the database, triggering a DatabaseVersion check

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              backlog-server-sharding Backlog - Sharding Team
              david.golden@mongodb.com David Golden
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: