Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Duplicate
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Storage Execution
Operating System:
ALL
Sprint:
Storage Execution 2026-02-16
CAR Domain/s:
None

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

It doesn't seem like we can incorrectly retrieve a nonzero size/count for these collections using the 'db.<collName>.count()' interface, presumably because of some higher level optimization when "collName" doesn't exist, but we should consider cleaning these entries so that the internal collection doesn't store size and count for all collections that we ever wrote to.

duplicates

SERVER-120541 Add and remove the collection size and count info on create and drop

Closed

related to

SERVER-120541 Add and remove the collection size and count info on create and drop

Closed

SERVER-125030 Add test coverage for deletes from the fast count store appearing in the applyOps entry for flushing

Closed

SERVER-126090 Complete TODO listed in SERVER-118821

Closed

Assignee:: Unassigned
Reporter:: Damian Wasilewicz
Participants:: Damian Wasilewicz
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Feb 03 2026 05:19:10 PM UTC
Updated:: May 06 2026 04:12:42 AM UTC
Resolved:: Apr 21 2026 05:32:55 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates