[DRIVERS-1397] Retryable reads for Atlas Search Created: 15/Sep/20 Updated: 22/Sep/21 |
|
| Status: | Blocked |
| Project: | Drivers |
| Component/s: | mongot, Retryability |
| Fix Version/s: | None |
| Type: | Epic | Priority: | Major - P3 |
| Reporter: | James Akins (Inactive) | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | mongot-cross-team | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Driver Changes: | Needed | ||||||||
| Description |
|
Epic Summary Summary Motivation Cast of CharactersEngineering Lead:
Documentation[Scope Document|some.url] |
| Comments |
| Comment by Marcus Eagan (Inactive) [ 19/Oct/20 ] |
|
A bit of business-minded context here: The lack of retryable reads for a feature used to query MongoDB for data contradicts some of our strongest selling points around MongoDB, like high availability and supporting development of micro services. The lack of retryable reads might make a company looking to adopt DevOps hesitant. Does anyone here have any thoughts about a meaningful work around? |
| Comment by Bernie Hackett [ 15/Sep/20 ] |
|
Some notes on the technical problem.
After a number of potential solutions were discussed the only solution that seemed reasonable was for mongod to return a retryable error that specified the retry should happen on a different server. This seems like a change to SDAM, Server Selection, and Retryable Reads, and will require changes in mongos to implement new versions of those specs and mongod to communicate a new retryable error type.. |
| Comment by Bernie Hackett [ 15/Sep/20 ] |
| Comment by James Akins (Inactive) [ 15/Sep/20 ] |
|
Note: the Atlas Search team would like the Drivers team to review this project for consideration for their FY21Q4 plan. In the meantime, please let us know if there are any questions we can help answer; thanks!
|