[SERVER-71757] Modify _configsvrAddShard() to include a notification on its completion to a remote shard node Created: 01/Dec/22  Updated: 21/Feb/23  Resolved: 21/Feb/23

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

Type: Task Priority: Major - P3
Reporter: Paolo Polato Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding EMEA
Participants:

 Description   

When an addShard() command gets committed by the config server, the event should be registered in the oplog of other shards of the cluster to ensure that mongos processes will eventually be notified.

The objective of this ticket is to ensure that _configsvrAddShard() includes a successful invocation of the command introduced in SERVER-71754 as part of its commit section.



 Comments   
Comment by Paolo Polato [ 21/Feb/23 ]

It has been agreed that addShard won't be described through a dedicated oplog entry - instead, already existing shards will emit op events for each database imported from the replica set being added (see SERVER-71755 for details).

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