[SERVER-4219] When a collection is sharded, mongods should be notified by the mongos Created: 07/Nov/11  Updated: 13/Dec/11  Resolved: 13/Dec/11

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

Type: Bug Priority: Major - P3
Reporter: Greg Studer Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-4388 newly sharded collection requires con... Closed
Operating System: ALL
Participants:

 Description   

This is somewhat of an optimization, as separate mongoses are not guaranteed to pick up the newly sharded collection at the same time, and there can be no data host changes until migrations occur (at which point the mongods will load the versions). However, it would be clearer if the mongods were notified, and would eliminate version checks for other mongoses with correct info about the current version.

Also should verify that a cursor opened on an unsharded collection is treated correctly if sharding occurs afterwards.


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