-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Engines, Storage Engines - Transactions
-
None
-
5
Implement proper locking mechanisms for the WT_PENDING_PREPARED_MAP hash map to ensure thread safety when multiple sessions access the same hash buckets.
- Consider bucket-level locking vs. global hash map locking for performance
- Evaluate impact on existing single-threaded performance
- Ensure lock ordering to prevent deadlocks
- Consider lock-free alternatives if performance is critical
- related to
-
WT-15330 Remove claimed prepared transactions from hash map
-
- Closed
-