There is a handful of warnings reported for accesses to has_stable_timestamp, stable_timestamp, has_oldest_timestamp and oldest_timestamp variables. See examples in the comments. Some of the accesses to (has_)stable_timestamp use acquire/release and some use relaxed, while (has_)oldest_timestamp always accessed through relaxed only.

Given that the part that uses acquire/release accesses was introduced as the part of the disagg merge, it's worth checking how these variables should be synchronised. This ticket could be potentially split to two different ones, one for oldest_timestamp and one for stable_timestamp, but I've decided to leave both of them here since they seem to represent the same access concept.

To reproduce the warnings, find all the FIXMEs in the code, remove the suppressions, and run TSAN variants in CI.