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

initial_sync_invalid_index_spec.js: Increase timeout and add handling for use3dot2InitialSync

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 3.4.0-rc1
    • None
    • Replication
    • None
    • Minor Change
    • Integration 2016-10-10
    • 0

    Description

      initial_sync_invalid_index_spec.js expects an invalid index specification option to cause members performing initial sync to abort on application. Currently the timeout is 60 seconds which is not sufficient for the initsync-3dot2-rhel-62 evergreen variant (as reported by BF-3671). We should increase the timeout to at least 120 seconds (if not the default of 5 minutes).

      Additionally the initsync-3dot2-rhel-62 evergreen variant abort is triggered by a different assertion than the normal path. Add handling to recognize this assertion.

      Attachments

        Activity

          People

            james.wahlin@mongodb.com James Wahlin
            james.wahlin@mongodb.com James Wahlin
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: