[SERVER-42901] Use LockerImpl for the startup code path instead of LockerNoop Created: 19/Aug/19 Updated: 27/Oct/23 Resolved: 05/Jul/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Gone away | Votes: | 1 |
| Labels: | groomed | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Description |
|
OperationContextNoop should be looked into as well. The only place it appears to be used in production is the StorageEngineImpl constructor, otherwise just testing.
|
| Comments |
| Comment by Kaloian Manassiev [ 05/Jul/23 ] |
|
Gone away as a result of |
| Comment by Dianna Hohensee (Inactive) [ 19/Aug/19 ] |
|
I recommend trying to do this, and if anything surprising arises to consider spinning off additional tickets and re-schedule this with the new information. |
| Comment by Dianna Hohensee (Inactive) [ 19/Aug/19 ] |
|
|