[SERVER-41493] Set request deadline based on maxtime ms in the network interface Created: 04/Jun/19 Updated: 29/Oct/23 Resolved: 01/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mira Carey | Assignee: | Shaileja Jain (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Service Arch 2019-07-15, Service Arch 2019-08-12 |
| Participants: |
| Description |
|
We sometimes have access to an opCtx when constructing a RemoteCommandRequest. That opCtx may in turn have a maxtimems deadline. By honoring that deadline (making the deadline the lesser of passed timeoutMillis and remaining time left on the opctx) we can convey important information to the connection pool and avoid returning connections to requesters that won't use them |
| Comments |
| Comment by Githook User [ 01/Aug/19 ] |
|
Author: {'name': 'Shaileja Jain', 'username': 'shailejajain', 'email': 'shaileja.jain@gmail.com'}Message: |