Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 7.0.0-rc0
Affects Version/s: None
Component/s: None
Labels:
- sharding-wfbf-day

Assigned Teams:

Sharding EMEA
Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Sharding EMEA 2023-04-03, Sharding EMEA 2023-04-17
Linked BF Score:
135
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 is problematic in a config catalog environment because CatalogClient::getCollection will perform a read with read concern majority with afterClusterTime against the config server. And since itself is the config server, it can get stuck waiting for the clusterTime since the node's opTime will not advance because it is still processing the collMod op, causing a cyclic dependency.

It is also not ideal that this call is performed while collection MODE_X is being held.

is caused by

SERVER-68769 If a shard key index cannot be dropped then a user should not be able to hide that index

Closed

SERVER-69429 Missing checks in collMod for shard key and unique index

Closed

is related to

SERVER-68769 If a shard key index cannot be dropped then a user should not be able to hide that index

Closed

Assignee:: Allison Easton
Reporter:: Randolph Tan
Participants:: Allison Easton, Githook User, Jack Mulrow, Randolph Tan
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Mar 14 2023 05:31:22 PM UTC
Updated:: Oct 29 2023 09:24:56 PM UTC
Resolved:: Apr 10 2023 01:21:52 PM UTC
Confidence Status Last Update:: 03/Apr/23 2:02 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates