[SERVER-65038] Ensure profiling works when write blocking is enabled Created: 29/Mar/22 Updated: 29/Oct/23 Resolved: 08/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jordi Serra Torrens | Assignee: | Jordi Serra Torrens |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2022-04-04, Sharding EMEA 2022-04-18 |
| Participants: |
| Description |
|
Profiling is not working when user writes are blocked because the write to 'db.system.profile' fails due the write blocking. Profiling should work even if user writes are blocked. |
| Comments |
| Comment by Githook User [ 08/Apr/22 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: |
| Comment by Jordi Serra Torrens [ 29/Mar/22 ] |
|
Repro of operations missing from the system.profile collection: write-blocking-and-profiling-repro.js Additionally, enabling profiling also may fail when user writes are blocked. I believe this is due to a failure when attempting to create the 'db.system.profile' collection. Repro: write-blocking-and-enable-profiling-repro.js |