[SERVER-77321] Add a uassert that bulkWrite commands run on mongos are ordered Created: 19/May/23 Updated: 29/Oct/23 Resolved: 22/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kaitlin Mahar | Assignee: | Kaitlin Mahar |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | milestone-2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Repl 2023-05-29 | ||||
| Participants: | |||||
| Linked BF Score: | 149 | ||||
| Description |
|
We don't currently support unordered bulkWrite on mongos, but it is possible for the fuzzer to generate unordered bulkWrite invocations to run there that cause the server to crash, e.g. if the invocation generates a StaleConfig error and leads to the case we plan to handle in We can add a uassert that checks only ordered bulkWrites are run on mongos for now to prevent further fuzzer failures until this behavior is properly supported. |
| Comments |
| Comment by Githook User [ 19/May/23 ] |
|
Author: {'name': 'Kaitlin Mahar', 'email': 'kaitlin.mahar@mongodb.com', 'username': 'kmahar'}Message: |