[SERVER-61153] findAndModify on mongos/mongoq handles TenantMigrationAborted Created: 01/Nov/21 Updated: 29/Oct/23 Resolved: 02/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.2.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Mathis Bessa |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Server Serverless 2021-11-15 |
| Participants: |
| Description |
|
findAndModify on mongos/mongoq checks for a routing error from the targeted shard here in its command body and throws if it finds one. The exception is caught here in mongos/mongoq, where mongos/mongoq retries the findAndModify. This ticket is to include TenantMigrationAborted in the list of routing errors that is checked, thrown, and caught. The existing jstest that findAndModify passes TenantMigrationAborted back to the client should be updated to assert the findAndModify now succeeds since mongos/mongoq retries internally. |
| Comments |
| Comment by Githook User [ 02/Nov/21 ] |
|
Author: {'name': 'mathisbessamdb', 'email': 'mathis.bessa@mongodb.com', 'username': 'mathisbessamdb'}Message: |