In WT-12032, we figured out that MongoDB is using the set_timestamp API with the force field.

MongoDB uses it in a way that the oldest timestamp becomes greater than the stable timestamp which can cause undesired issues. To diagnose issues related to such usage of the API, it would be great to:

• Track with a new statistic the usage of the set_timestamp API along with the force field.
• Track whenever the stable and oldest timestamps are not in order. We may want to expand this to other timestamps.
• Log a warning when ooo ts is detected after calling set_timestamp.