-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Storage Execution 2025-03-03, Storage Execution 2025-03-31, Storage Execution 2025-04-14
-
None
-
None
-
None
-
None
-
None
-
None
-
None
This behavior is simple to describe, but potentially tedious to setup correctly. However, it would open up many avenues to expand our unit testing of the bucket catalog which is hard to reason about. Examples:
- Fill bucket with measurements (without closing it)
- Fill N buckets in the same stripe (without closing them)
- Create N buckets in the same stripe
- Essentially, make the bucket -> stripe hashing system easy to work with.
Scenarios that could use these primitives:
- An insert leads to the closing of many buckets with various bucket catalog APIs
- Are all these APIs resilient to one versus many buckets in various states?
- Reproduce high stripe contention states and perform operations
- depends on
-
SERVER-101358 Add _fillBucketWithMeasurements and _createBucketsWithMeasurements bucket catalog unit test primitive
-
- Open
-
-
-
- Closed
-
- is related to
-
-
- Open
-
- related to
-
SERVER-100221 Create a clarified interface to reopen bucket from disk
-
- Closed
-