Investigate failing ContinuousAddRemoveShard hook in TSAN variants

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • 200
    • 2
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      When suites with ContinuousAddRemoveShard hook are executed on evergreen, for example as following

      evergreen patch --project mongodb-mongo-master --variants all --regex_tasks='.*add_remove_shard.*' --auto-description --finalize

      they can fail time to time with different unexpected errors on slow variants like TSAN. Typical errors:

      ShardingStateNotInitialized (203)
      UnsatisfiableWriteConcern (100) (usually with fuzzer suites)
      UserWritesBlocked(371) (usually with fuzzer suites)
      during different move commands.

      Investigate the root cause for these errors and a possibility to make suites more stable.

            Assignee:
            Unassigned
            Reporter:
            Igor Praznik
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: