[SERVER-71755] Emit an oplog entry from an existing shard when a new database is added to the config catalog Created: 01/Dec/22  Updated: 29/Oct/23  Resolved: 27/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: Paolo Polato Assignee: Paolo Polato
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2022-12-26, Sharding EMEA 2023-01-09, Sharding EMEA 2023-01-23, Sharding EMEA 2023-02-06, Sharding EMEA 2023-02-20, Sharding EMEA 2023-03-06, Sharding EMEA 2023-03-20, Sharding EMEA 2023-04-03
Participants:

 Description   

When a database gets added to the config catalog (through explicit/implicit db creation, or as the consequence of invoking addShard() on a replica set with existing user data) an event should be registered in the oplog of other shards of the cluster to ensure that mongos processes will eventually be notified.

The purpose of this ticket is to implement the command introduced in SERVER-71754 so that its recipient will emit the oplog entry type introduced in SERVER-71621 on each invocation.



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

Author:

{'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}

Message: SERVER-71755 Modify enableSharding and addShard to support database placement history
Branch: master
https://github.com/mongodb/mongo/commit/c463c8c8aee2da1a0bb30a846cb57b85494f4f93

Comment by Paolo Polato [ 16/Feb/23 ]

Moving the ticket back to the "in progress" state, following a change to the proposed design.

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