[SERVER-21005] Consistent maxTimeMs / timeout / interruption support Created: 19/Oct/15 Updated: 14/Feb/19 Resolved: 14/Feb/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Andy Schwerin | Assignee: | Blake Oler |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | gm-ack | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Sprint: | Sharding 2019-02-25 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
While maxTimeMs is for providing soft deadlines for operations, the server could do a much better job adhering to those deadlines and better support interruption without major architectural changes. The purpose of this project is to make maxTimeMs deadline-oriented, and to improve its behavior when operations involve several nodes communicating (as in sharding). |
| Comments |
| Comment by Blake Oler [ 14/Feb/19 ] |
|
Closing this as work covered by |
| Comment by Andy Schwerin [ 19/Oct/15 ] |
|
This jira search matches a number of relevant maxTimeMs tickets. |