[SERVER-33401] Refuse to start up v4.0 shards if config.cache.collections or config.collections entries lack UUIDs Created: 20/Feb/18  Updated: 23/Feb/18  Resolved: 23/Feb/18

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

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Kaloian Manassiev
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-33356 Ensure shards' persisted collection c... Closed
Sprint: Sharding 2018-03-12
Participants:

 Description   

Replication Change Streams relies on the presence of UUIDs, even though Sharding code doesn't yet rely on the presence of UUIDs.



 Comments   
Comment by Kaloian Manassiev [ 21/Feb/18 ]

This ticket is related to SERVER-33356. I would just do the first part of it, which ensures that the config server config.collection entries always contain UUIDs.

The assignment of UUIDs on the per-shard cache collections will happen as part of SERVER-33356.

Comment by Dianna Hohensee (Inactive) [ 21/Feb/18 ]

This may or may not require test work arounds due to SERVER-33356. If so, temporarily dropping the persisted cache collections for tests doing binary upgrades should work.

Generated at Thu Feb 08 04:33:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.