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

Determine if splitvector.js should be blacklisted from the retryable_writes_jscore_stepdown_suite

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.6.8, 3.7.4
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v3.6
    • Sprint:
      Sharding 2018-04-09
    • Linked BF Score:
      0

      Description

      jstests/core/splitvector.js occasionally times out on slower buildvariants in the retryable_writes_jscore_stepdown_suite. Even when successful, this is consistently the slowest test in this suite by a long shot (only ~8 min on Enterprise RHEL 6.2, > 1 hour on Linux DEBUG, ~ 1 hour on Windows 2008R2 DEBUG).

      This is expected because the test performs 10s of thousands of inserts and at least a dozen splitvectors. We can blacklist the test to avoid these timeouts, but the test itself isn't failing, and we'd lose some test coverage and some stepdown stress testing (longer runs can have ~400 failovers).

      The purpose of this ticket is to determine if its worth blacklisting splitvector.js or if we should find another way to avoid the timeouts.

        Attachments

          Activity

            People

            Assignee:
            jack.mulrow Jack Mulrow
            Reporter:
            jack.mulrow Jack Mulrow
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: