ExportXMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      almost all the current FSM concurrency workloads do not test concurrent reshardings because they only allow thread 0 to issue resharding operations. we want to test concurrent resharding as of SERVER-136621, so we should update these tests to remove the constraint that only a single thread issues resharding operations, and we should consider writing a new test with higher weights on the threads issuing resharding operations.

      we also want to update the tolerance towards accepting the ConflictingOperationInProgress error (and ReshardCollectionInProgress). if the feature is enabled, we shouldn't assert on this error appearing.

      similarly, we want to check for moveCollection and unshardCollection tests to update them similarly.

            Assignee:
            Unassigned
            Reporter:
            Anja Kalaba
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: