[SERVER-61224] Investigate retryability of collMod command in mongos Created: 03/Nov/21 Updated: 18/Nov/21 Resolved: 18/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Yuhong Zhang |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Execution Team 2021-11-29 | ||||||||
| Participants: | |||||||||
| Description |
|
Most of the collMod tests in our codebase are tagged with requires_non_retryable_commands (see example in collmod_convert_to_ttl.js). In this ticket, we attempt to explore and clarify the semantics around retrying collMod operations in a sharded configuration.. |
| Comments |
| Comment by Yuhong Zhang [ 18/Nov/21 ] |
|
After the discussion with Sharding EMEA we decided to leave the retry logic to the replicator as it will need to handle the retries like other drivers on replica sets as well. There are also other ongoing work like PM-2583 and |
| Comment by Benety Goh [ 03/Nov/21 ] |
|
This ticket was raised while reviewing |