[SERVER-62948] Ensure FTDC collectors don't have a read timestamp Created: 25/Jan/22 Updated: 29/Oct/23 Resolved: 26/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0, 5.2.1, 4.4.13, 5.0.7 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Gregory Noma |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Requested: |
v5.2, v5.0, v4.4
|
||||||||
| Sprint: | Execution Team 2022-02-07 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
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. |
| Comments |
| Comment by Githook User [ 10/Feb/22 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: (cherry picked from commit 3b31903d7ba72e8c9cc3e64b7dc0617cc26e0ecc) |
| Comment by Githook User [ 10/Feb/22 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: (cherry picked from commit 3b31903d7ba72e8c9cc3e64b7dc0617cc26e0ecc) |
| Comment by Githook User [ 10/Feb/22 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: |
| Comment by Githook User [ 26/Jan/22 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: |