[SERVER-45103] Sharded index commands shouldn't target primary shard if it doesn't own chunks Created: 12/Dec/19  Updated: 29/Oct/23  Resolved: 13/Dec/19

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

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

Issue Links:
Related
related to SERVER-62310 collMod command not sent to all shard... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2019-12-16
Participants:

 Description   

Since SERVER-44720 was implemented, the requirement that the primary shard for a sharded collection always has correct indexes even when it owns no chunks has been dropped, so the logic to always target the primary shard should be removed.



 Comments   
Comment by Githook User [ 13/Dec/19 ]

Author:

{'name': 'Cheahuychou Mao', 'email': 'cheahuychou.mao@mongodb.com', 'username': 'cheahuychou'}

Message: SERVER-45103 Sharded index commands shouldn't target primary shard if it doesn't own chunks
Branch: master
https://github.com/mongodb/mongo/commit/ece2e8f36cff8f996ae584708a9dab80b6419e63

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