[DRIVERS-1501] Crash-Resilient Versioned Fast Counts Created: 11/Jan/21  Updated: 22/Sep/21  Resolved: 20/Jan/21

Status: Closed
Project: Drivers
Component/s: None
Fix Version/s: None

Type: Epic Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Driver Changes: Not Needed

 Description   
Downstream Change Summary

Documentation changes expected for cached counts. There are also support cases that may be affected.

Description of Linked Ticket

Epic Summary

Summary

The server code currently stores a cached count of the total number of documents in each collection, for fast access.  Certain situations involving unclean shutdowns (when the server crashes) can leave these fast-count values inaccurate. This project will develop an idea to improve this logic in order to avoid inaccuracies in the fast-counts for collections.

Motivation

Accurate fast counts are important, since they are not only consumed by user queries but also internal processes (e.g. sharding). We currently document that fast counts can be inaccurate, but for the users that happen to miss this unexpected detail, it's a form of data corruption.

Cast of Characters

  • Product Owner: Michael Gargiulo
  • Project Lead:
  • Program Manager: Connie Chen
  • Drivers Contact:

Documentation

Scope Document
Technical Design Document


Generated at Thu Feb 08 08:23:30 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.