-
Type:
Bug
-
Resolution: Gone away
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
ALL
-
Storage Execution 2025-09-29
-
200
-
None
-
None
-
None
-
None
-
None
-
None
-
None
1) We perform an insert request into a time-series collection here
2) We perform queries through DBClient to find buckets to reopen here and here
3) We call in to DBClient and re-use the same OperationContext here.
4) While processing the request we set the rawDataOperation value for the request to true here
5) At this point, we may encounter an error because setting FCV now takes the critical section following SERVER-103711; this causes us to retry the request which would throw in the service entry point shard role here.
6) We call back in to retry the insert request, but now the rawDataOperation value is still true since it was not reset, and we try to insert the measurements into the buckets collection as if it were a raw data operation.
The insert will ultimately fail because the document will fail the bucket schema validator.
- is related to
-
SERVER-109715 Make cloneAuthoritativeMetadata DDL avoid holding the critical section when cloning metadata
-
- Closed
-
-
SERVER-103711 Replace setter methods from DatabaseShardingRuntime with a new dedicated class
-
- Closed
-
- related to
-
SERVER-109839 Running sub-queries with the same OperationContext can lead to unexpected behavior upon retrying
-
- Open
-
-
SERVER-111099 Temporarily exclude bucket_unpacking_with_sort_negative from fcv_upgrade_downgrade_sharding_jscore_passthrough suite
-
- Closed
-