[SERVER-72410] Single global telemetry store Created: 28/Dec/22 Updated: 29/Oct/23 Resolved: 04/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jess Balint | Assignee: | Jess Balint |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | QO 2023-01-09 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 110 | ||||||||||||
| Description |
|
We initially planned to clear the telemetry data in response to user request. In support of this, we introduced a read/write locking scheme around the telemetry store. It's complexity has since proven that we additional design around interaction with op ctx. The clearing of the telemetry store is now an outdated requirement. We can replace the current implementation with a single global telemetry store. In the future, we can re-design it to handle clearing if necessary. |
| Comments |
| Comment by Githook User [ 30/Dec/22 ] |
|
Author: {'name': 'Jess Balint', 'email': 'jbalint@gmail.com', 'username': 'jbalint'}Message: |