Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 6.3.0-rc0
Affects Version/s: 6.1.1, 6.2.0-rc6
Component/s: Sharding
Labels:
- shardingemea-qw

Backwards Compatibility:
Fully Compatible
Backport Requested:

v6.0, v5.0, v4.4
Sprint:
Sharding EMEA 2022-11-28, Sharding EMEA 2022-12-12, Sharding EMEA 2022-12-26, Sharding EMEA 2023-01-09, Sharding EMEA 2023-01-23, Sharding EMEA 2023-02-06
Case:
Story Points:
3.33
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

Database metadata refresh should not take the database lock in MODE_X. Instead, we should be able to do it under MODE_IX. This prevents database metadata refreshes from blocking behind ongoing transactions. This is similar to what ~~SERVER-40258~~ did for collection metadata refreshes.

is caused by

SERVER-64209 Push the DatabaseShardingState state to the Storage Catalog

Closed

related to

SERVER-73345 Cancel ongoing refresh on DB metadata cleanup

Closed

SERVER-40258 Relax locking requirements for sharding metadata refresh on shards

Closed

Assignee:: Antonio Fuschetto
Reporter:: Jordi Serra Torrens
Participants:: Antonio Fuschetto, Githook User, Jordi Serra Torrens
Votes:: 0 Vote for this issue
Watchers:: 12 Start watching this issue

Created:: Oct 25 2022 01:38:33 PM UTC
Updated:: Apr 03 2024 03:56:41 AM UTC
Resolved:: Jan 30 2023 11:17:12 AM UTC
Confidence Status Last Update:: 25/Jan/23 12:08 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates