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

Reenable random chunk migration failpoint for concurrency with_balancer suites

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: None
    • Labels:
      None
    • Sprint:
      Sharding 2019-12-16, Sharding 2019-12-30, Sharding 2020-01-13

      Description

      The random migration failpoints have possible exposed various failures and will be disabled until we investigate the BFs that were encountered. Once we have resolved these issues, the failpoint should be reenabled.

        Attachments

          Issue Links

          depends on

          Bug - A problem which impairs or prevents the functions of the product. SERVER-43106 Test create_index_background_wildcard.js doesn't account for orphans when run with random migrations

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-43196 Blacklist update_where.js from sharded concurrency suites with balancer on and no txn override

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

          Task - A task that needs to be done. SERVER-42914 Implement random chunk selection policy for balancer for use in concurrency_*_with_balancer workloads

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

            Activity

              People

              Assignee:
              backlog-server-sharding Backlog - Sharding Team
              Reporter:
              alex.taskov Alexander Taskov
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated: