Loading...

XML

Word

Printable

JSON

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

Assigned Teams:

Sharding EMEA
Backwards Compatibility:
Fully Compatible
Sprint:
Sharding EMEA 2023-10-30, CAR Team 2023-11-13
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

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

Currently we have a feature flag that when disabled prevent all the work in PM-3364 to fully take effect, specifically, when disabled, we don't allow unsplittable collections to live in non primary shards.

This behavior is transient, while PM-3364 dependent work is completed and queries can use the information of the single chunk on unsplittable collections to route queries. Once we have full compatibility, we can completely remove the feature flag, and leave the desired behavior (allow unsplittable collections to live in non primary shards) to be the default behavior.

depends on

SERVER-79667 Investigate if changes are needed on CollectionRoutingInfoTargeter to support tracked unsharded timeseries

Closed

SERVER-80420 Make mongos' findAndModify command able to target tracked unsplittable collections

Closed

is depended on by

SERVER-82239 Complete TODO listed in SERVER-80337

Closed

is duplicated by

SERVER-80337 Stop ignoring ShardVersion::UNSHARDED for unsplittable collections

Closed

Assignee:: Allison Easton
Reporter:: Marcos José Grillo Ramirez
Participants:: Allison Easton, Githook User, Marcos José Grillo Ramirez
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Sep 07 2023 10:41:20 AM UTC
Updated:: Nov 03 2023 07:36:29 AM UTC
Resolved:: Nov 03 2023 07:36:28 AM UTC
Confidence Status Last Update:: 19/Oct/23 8:36 AM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates