[SERVER-81161] Cluster query and write without shard key commands should log at higher verbosity Created: 18/Sep/23 Updated: 29/Oct/23 Resolved: 25/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jason Zhang |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Sharding NYC
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding NYC 2023-10-02 | ||||
| Participants: | |||||
| Description |
|
Both cluster query without shard key and cluster write without shard key log that they are running at the default verbosity level, so each updateOne without shard key will log at least twice. We could raise the debug level for these logs so they don't run by default, which should reduce log spam and slightly improve performance. |
| Comments |
| Comment by Githook User [ 25/Sep/23 ] |
|
Author: {'name': 'Jason Zhang', 'email': 'jason.zhang@mongodb.com', 'username': 'jz1242'}Message: |