[SERVER-51693] DBClientConnection should require an appName Created: 16/Oct/20 Updated: 16/Jan/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Benjamin Caimano (Inactive) | Assignee: | Backlog - Service Architecture |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | lowcontext, servicearch-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Service Arch
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Participants: | |||||
| Story Points: | 2 | ||||
| Description |
|
As is, DBClientConnection takes in an applicationName here. But it never verifies that the applicationName is not empty. We should invariant that it isn't empty and change locations that were using empty applicationNames. This would allow us to explicitly see when shardsvr commands are on behalf of internal services like initial sync.
Acceptance criteria: Change appNames to be non empty (e.g. (_FILE_) and log a warning when they are empty. |
| Comments |
| Comment by Lauren Lewis (Inactive) [ 24/Feb/22 ] |
|
We haven’t heard back from you for at least one calendar year, so this issue is being closed. If this is still an issue for you, please provide additional information and we will reopen the ticket. |