[SERVER-73409] Handle tenant migrations for a catalog shard Created: 27/Jan/23  Updated: 29/Oct/23  Resolved: 06/Mar/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Jack Mulrow Assignee: Jack Mulrow
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-74977 Complete TODO listed in SERVER-73409 Closed
is related to SERVER-72142 Define catalog shard changelog behaviour Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding NYC 2023-02-06, Sharding NYC 2023-02-20, Sharding NYC 2023-03-06
Participants:

 Comments   
Comment by Githook User [ 04/Mar/23 ]

Author:

{'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}

Message: SERVER-73409 Continue disallowing tenant migration commands on config servers
Branch: master
https://github.com/mongodb/mongo/commit/c10e86a714918f2747999bf2bfc4814a1cf50161

Comment by Jack Mulrow [ 03/Mar/23 ]

From talking with didier.nadeau@mongodb.com and milkie@mongodb.com on slack, we don't expect to use colocated config servers in serverless soon, so for now it's fine to keep disallowing the tenant migration commands on a config server. We can lift that restriction later, when we know if it's necessary.

So this ticket should now track updating the tenant migration command cluster role checks (like this one) to continue throwing when on a config server even when it's capable of acting as a shard.

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