[SERVER-72395] random_moveChunk_multi_update_delete_change_streams.js should create the 'operations' collection during its setup phase Created: 23/Dec/22 Updated: 29/Oct/23 Resolved: 09/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jordi Serra Torrens | Assignee: | Jordi Serra Torrens |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Sharding EMEA
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding EMEA 2023-01-09 | ||||
| Participants: | |||||
| Linked BF Score: | 20 | ||||
| Description |
|
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. |
| Comments |
| Comment by Githook User [ 09/Jan/23 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: |