[SERVER-81553] Support isMaster against any database, irrespective of the tenant domain Created: 28/Sep/23  Updated: 02/Feb/24

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Sophia Tan Assignee: Backlog - Service Architecture
Resolution: Unresolved Votes: 0
Labels: ntdi_must_have, ntdi_releasability
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Gantt Dependency
has to be done before SERVER-84696 Revert SERVER-80753 Closed
Related
is related to SERVER-84666 Shift DatabaseName parsing from OpMsg... Blocked
Assigned Teams:
Service Arch
Sprint: Service Arch 2023-10-16, Service Arch 2023-10-30, Service Arch 2023-11-13, Service Arch 2023-11-27, Service Arch 2023-12-11, Service Arch 2023-12-25, Service Arch 2024-01-08, Service Arch 2024-01-22
Participants:
Story Points: 2

 Description   

The `isMaster` command can run on any db (including the non-existing db) in non multitenancy environment.
We found it cannot run on external db (eg, "myDb") without tenant information in multitenancy environment as mongod takes this db name as an invalid db name (missing tenant id). It does not make sense. We should support it against any db, irrespective of the tenant domain.


Generated at Thu Feb 08 06:46:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.