[SERVER-84372] Allow to configure the NoOpWriter frequency with finer granularity Created: 21/Dec/23 Updated: 22/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Paolo Polato | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Execution
|
| Participants: |
| Description |
|
Today, users have the possibility to customise the the frequency of oplog entries emitted by the NoOpWriter through the periodicNoopIntervalSecs server parameter, which allows to express a value at "seconds" granularity within the [1, 10] range. These traits could nevertheless be insufficient to cover all use cases - in particular, "sub-second" periods could be desirable for specific deployments. |