-
Notifications
You must be signed in to change notification settings - Fork 355
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revisit the Monitoring feature #4152
Comments
There are many residual AggregatedValueObject instances that are not trim. These objects are holded by AggregatedSlidingWindowTimeReservoir. Adding some log lines it is possible to see the issue. In the lines we can see many instances of AggregatedSlidingWindowTimeReservoir. Something is not working properly because there are PUTs of AggregatedValueObject in many AggregatedSlidingWindowTimeReservoir, but it only trims in one. This causes residual AggregatedValueObject instances that can be seen when you run a heapdump.
AggregatedSlidingWindowTimeReservoir@35a4060f is fully cleaned, but the other instances still contains AggregatedValueObject. Edit: In the constructor: And additionally, there is:
That TRIM_THRESHOLD is 256, so it only trims once AggregatedSlidingWindowTimeReservoir contains 256 AggregatedValueObject. The number of instances of AggregatedSlidingWindowTimeReservoir is something that I still need to investigate. |
The text was updated successfully, but these errors were encountered: