[SERVER-80711] Investigate giving setFCV command kImmediate priority Created: 04/Sep/23 Updated: 05/Sep/23 Resolved: 05/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jordi Olivares Provencio | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
In a conversation stemming from Currently the command will acquire a ticket since it has normal priority. It could be argued that the command is important enough to warrant a higher priority. |
| Comments |
| Comment by Gregory Noma [ 05/Sep/23 ] |
|
Typically immediate priority is only used for operations which are necessary for the system to make progress or for observability |