Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 5.2.0, 5.0.5, 5.1.1
Affects Version/s: 5.0.0
Component/s: Storage
Labels:
None

Backwards Compatibility:
Fully Compatible
Backport Requested:

v5.1, v5.0
Sprint:
Execution Team 2021-08-09, Execution Team 2021-11-01, Execution Team 2021-11-15
Linked BF Score:
153
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

Copying the CollectionCatalog is expensive. When there are tens of thousands of collections, operations like rollback become substantially slower. When the server is rolling back to the stable timestamp, the global lock is held in exclusive mode. We should be able to avoid making multiple copies of the collection catalog.

is related to

SERVER-59065 CatalogStats uses unsafe CollectionCatalog pointer during startup

Closed

SERVER-59591 LockerNoop::isW() always returns true allowing multiple operations think they are holding the global exclusive lock at the same time

Closed

SERVER-59819 collection_catalog_bm setup causes timeout

Closed

SERVER-60462 Global MODE_IS lock is required to access CollectionCatalog::get() in time-series code path

Closed

SERVER-60460 Add invariant to check that global lock is held when calling CollectionCatalog::get

Closed

SERVER-62618 Avoid quadratic behavior at startup with many collections

Closed

(1 is related to)

Assignee:: Henrik Edin
Reporter:: Gregory Wlodarek
Participants:: Githook User, Gregory Wlodarek, Henrik Edin
Votes:: 0 Vote for this issue
Watchers:: 11 Start watching this issue

Created:: Jul 21 2021 06:44:20 PM UTC
Updated:: Oct 29 2023 09:50:36 PM UTC
Resolved:: Nov 05 2021 01:44:30 PM UTC
Confidence Status Last Update:: 03/Nov/21 6:10 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates