-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Cursors
-
Security Level: Public (Available to anyone on the web)
-
Storage Engines, Storage Engines - Foundations
-
819.595
-
SE Foundations - 2026-04-10, SE Foundations - 2026-04-24, SE Foundations - 2026-05-08
-
None
Attached is a python test that creates ten layered tables - and in a loop: 1) puts data into some of the tables 2) checkpoints 3) picks up checkpoint 4) reads the data. All the data reads/writes do open_cursor/operation/close_cursor to emulate mongod usage. We expect that all cursors are cached, and that only the stable cursors on follower need to be recreated at checkpoint pickup. But according to stats, we are creating lots of new cursors (i.e. not cached) on both leader and follower, as if caching wasn't working or disabled.
Possibly a problem with the test, but the perf tiger team has seen a large steady number of cursor creates, not just at checkpoint pickup as expected. That would align with what we're seeing in this test.
- is related to
-
-
- Backlog
-