Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 7.1.0-rc0
Affects Version/s: None
Component/s: None
Labels:
- PM-3364-Milestone-0

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding EMEA 2023-07-24, Sharding EMEA 2023-08-07
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

This change is needed to be able to differentiate between unsharded and sharded collections: since they will both be registered on the sharding catalog, the new field (to be added here) will be set to true when needing to represent unsharded collections that are technically not allowed to be split.

Additionally to adding the new field, adapt the ChunkManager and the ShardCollectionType in order to take into account the new parameter (~~SERVER-75302~~ - that removed some fields from those components - can serve as an example to understand where to plug the new field).

is depended on by

SERVER-78756 Filter out `unsplittable` field on balancer paths

Closed

SERVER-78763 Allow create collection coordinator registering unsplitable collections

Closed

SERVER-78765 RoutingTableConsistencyChecker and CheckMetadataConsistency must account for tracked unsharded collections

Closed

SERVER-79157 Change create collection coordinator to allow sharding unsplittable collections

Closed

SERVER-79160 Track unsharded collections when adding a shard

Closed

SERVER-79178 Make necessary routing table changes to consider the splittable field

Closed

(1 is depended on by)

Assignee:: Enrico Golfieri
Reporter:: Pierlauro Sciarelli
Participants:: Enrico Golfieri, Githook User, Pierlauro Sciarelli
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Jul 07 2023 06:19:48 AM UTC
Updated:: Oct 29 2023 09:19:08 PM UTC
Resolved:: Jul 25 2023 08:32:27 AM UTC
Confidence Status Last Update:: 10/Jul/23 12:21 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates