Each time FTDC runs, it creates an OperationContext and ensures that it is configured to read at kNoTimestamp. However, it is theoretically possible that something could set a read timestamp on the OperationContext used by the collectors. We may want to consider adding an invariant within the loop through all collectors to try to guard against this.
- Votes:
-
0 Vote for this issue
- Watchers:
-
4 Start watching this issue
- Created:
- Updated:
- Resolved: