[SERVER-55026] Make tenant_migration_concurrent_reads_on_donor.js only send read with maxTimeMS if it is expected to block Created: 08/Mar/21 Updated: 29/Oct/23 Resolved: 08/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Cheahuychou Mao | Assignee: | Cheahuychou Mao |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding 2021-03-08, Sharding 2021-03-22 | ||||
| Participants: | |||||
| Linked BF Score: | 21 | ||||
| Description |
|
We shouldn't attach maxTimeMS to the linearizable read in the blocking state since it's not expected to block. Also, if the noop write for the linearizable read takes a long time to complete, the read could end up failing with MaxTimeMSExpired (see BF-20362). |
| Comments |
| Comment by Githook User [ 08/Mar/21 ] |
|
Author: {'name': 'Cheahuychou Mao', 'email': 'mao.cheahuychou@gmail.com', 'username': 'cheahuychou'}Message: |