[SERVER-81006] Handle local errors executing retryable timeseries updates in bulkWrite Created: 12/Sep/23 Updated: 29/Oct/23 Resolved: 08/Oct/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kaitlin Mahar | Assignee: | Lingzhi Deng |
| 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-09-18, Repl 2023-10-02, Repl 2023-10-16 | ||||||||
| Participants: | |||||||||
| Description |
|
Currently our logic for retryable timeseries updates assumes we get a response from a shard and doesn't know how to handle local errors: https://github.com/mongodb/mongo/blob/cf78d87ee503ecb877d261c9138d786b0b3b399f/src/mongo/s/write_ops/bulk_write_exec.cpp#L384-L385 The logical change should be simple: call through to the new |
| Comments |
| Comment by Githook User [ 07/Oct/23 ] |
|
Author: {'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}Message: |
| Comment by Lingzhi Deng [ 25/Sep/23 ] |
|
We should also handle top-level errors returned by the internal txn api for retryable timeseries update. |