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

Add concurrency workload framework to triggers various node failovers

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding, Testing Infrastructure
    • None
    • Sharding
    • Sharding B (10/30/15), Sharding D (12/11/15), Sharding E (01/08/16)

      We'd like to introduce a concurrency/FSM workload that triggers config server failovers to verify that they occur transparently to clients.

      Basic implementation notes:

      • Add a new workload to jstests/concurrency/fsm_workloads/ that randomly steps down / freezes / etc. the config server primary
        • Note: You may want to prevent the workload from running with itself
      • Modify jstests/concurrency/fsm_libs/runner.js to support "persistent" workloads that run in each schedule

      Here's what a schedule looks like now:

      [ [ "jstests/concurrency/fsm_workloads/update_array_noindex.js" ], [ "jstests/concurrency/fsm_workloads/update_multifield_isolated_multiupdate_noindex.js" ], [ "jstests/concurrency/fsm_workloads/update_rename_noindex.js" ]...

      Here's what the schedule should look like after:

      [ [ "jstests/concurrency/fsm_workloads/update_array_noindex.js", "jstests/concurrency/fsm_workloads/config_server_failover.js" ], [ "jstests/concurrency/fsm_workloads/update_multifield_isolated_multiupdate_noindex.js", "jstests/concurrency/fsm_workloads/config_server_failover.js" ], [ "jstests/concurrency/fsm_workloads/update_rename_noindex.js", "jstests/concurrency/fsm_workloads/config_server_failover.js" ]...

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            kamran.khan Kamran K.
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: