[SERVER-41474] Exclude database profiling from Flow Control Created: 03/Jun/19 Updated: 29/Oct/23 Resolved: 09/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Maria van Keulen | Assignee: | Maria van Keulen |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Execution Team 2019-07-15 |
| Participants: |
| Description |
|
IX lock acquisitions during database profiling should be explicitly excluded from Flow Control because the system.profile collection is non-replicated and will thus writes to it do not generate replication lag. |
| Comments |
| Comment by Githook User [ 09/Jul/19 ] |
|
Author: {'name': 'Maria van Keulen', 'email': 'maria@mongodb.com', 'username': 'mvankeulen94'}Message: |