[SERVER-77799] Test various error classes on mongos Created: 05/Jun/23 Updated: 30/Jan/24 Resolved: 30/Jan/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Vishnu Kaushik | Assignee: | Sean Zimmerman |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | milestone-2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Sprint: | Repl 2023-10-16, Repl 2023-11-13, Repl 2023-11-27 |
| Participants: |
| Description |
|
Test that that mongos can handle the error classes listed in the document (see comments). |
| Comments |
| Comment by Sean Zimmerman [ 30/Jan/24 ] |
|
I audited our existing testing and feel that our retryable writes testing is adequate. We have unit tests to ensure that stmtId is correctly attached to subbatches that are sent to mongod (where actual retryable writes behavior lives). Our sharded bulkwrite concurrency suite will also include internal_transactions_unsharded.js which does retryable writes against mongos. The only thing I could see we might be missing coverage for is bulkWrite + resharding but I don't think there is any special behavior there like for chunk migrations. |
| Comment by Kaitlin Mahar [ 20/Nov/23 ] |
|
I am tabling this in favor of picking up some higher priority work. The work left here is to look more into retryable writes testing and identify testing gaps. Adding some relevant Jira discussions in comments |
| Comment by Kaitlin Mahar [ 15/Nov/23 ] |
|
From my investigation so far I think we mostly have this covered perhaps with the exception of retryable errors. Notes so far (will add more on retryable errors tomorrow):
|