-
Type:
Task
-
Resolution: Gone away
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Concurrency
-
None
-
Storage Engines - Persistence
-
330.472
-
SE Persistence backlog
-
None
WT-16050 change to use acquire release semantics for these two variables as it is the strongest ordering in the internal wt api. However, I suspect it is still not enough and we need sequential consistency here as we are synchronising across multiple variables (btree->sync_session, btree->syncing, and the checkpoint generation).
Investigate what is the required memory ordering for these variables.