random_moveChunk_multi_update_delete_change_streams.js should create the 'operations' collection during its setup phase

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Sharding EMEA
    • Fully Compatible
    • Sharding EMEA 2023-01-09
    • 20
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When running in transaction suites, random_moveChunk_multi_update_delete_change_streams.js implicitly creates a collection (named 'operations') in the same transaction as the multi-update/multi-delete. Creating collections is not allowed in transactions that span more than one shard. The solution can be to make sure the 'operations' collection is created during the '$setup' phase before the test starts.

            Assignee:
            Jordi Serra Torrens
            Reporter:
            Jordi Serra Torrens
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: