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

Consider removing the sharding continuous stepdown suite

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None

    Description

      The sharding continuous stepdown suite was introduced in MongoDB 3.2 as a way to test CSRS and over time has surfaced numerous sharding and replication bugs. At that time, the sharding metadata commands were all implemented on mongos and were doing reads and writes against the config server.

      As of MongoDB 3.6 however, most of the metadata commands have been moved to run on the config server primary. As a result of this, the continuous stepdown suite has now become a test of the repeatability of these operations in the context of running sharding tests. However, due to the different command return values which can happen after an operation is repeated, this suite is now generating build failures, which are not necessarily bugs, but behaviour, which is not expected by tests and making tests account for this behaviour is not a trivial task, nor it is something which has a great customer value.

      Because of this I would like to propose that we get rid of the sharding continuous stepdown suite in lieu of the already running concurrency stepdown suite.

      Attachments

        Activity

          People

            max.hirschhorn@mongodb.com Max Hirschhorn
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: