Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 7.1.0-rc0, 7.0.2, 5.0.22, 6.0.11
Affects Version/s: None
Component/s: None
Labels:
- sharding-nyc-subteam3

Assigned Teams:

Sharding NYC
Backwards Compatibility:
Fully Compatible
Backport Requested:

v7.0, v6.0, v5.0
Sprint:
Sharding NYC 2023-07-10, Sharding NYC 2023-07-24, Sharding NYC 2023-08-07
Linked BF Score:
160
Story Points:
2
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

The hashed index is only needed to support chunk migrations. However, it hurts write performance. Most collections with hashed shard keys have even data distribution and growth, thus not requiring chunk migrations. As such, we should allow customers to drop the hashed index for hashed shard keys.

is depended on by

SERVER-78995 Allow users to hide the last compatible hashed shard key index

Closed

is related to

SERVER-99654 Disallow dropping hashed shard key in case of pending range deleter tasks

Backlog

related to

SERVER-78863 Audit places in the codebase that rely on the hashed index to ensure correct behavior.

Closed

SERVER-78252 Block chunk migrations for hashed shard keys if you don’t have the shard key index

Closed

Assignee:: Ali Mir
Reporter:: Garaudy Etienne
Participants:: Ali Mir, Garaudy Etienne, Githook User, Max Hirschhorn, Randolph Tan
Votes:: 0 Vote for this issue
Watchers:: 10 Start watching this issue

Created:: Jun 20 2023 08:15:25 PM UTC
Updated:: Jan 21 2025 05:02:04 PM UTC
Resolved:: Aug 02 2023 07:37:59 PM UTC
Confidence Status Last Update:: 25/Jul/23 7:27 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates