You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is high memory usage during the APIM Analytics server restart. During the investigation, we found that this issue occurs because the analytics server tries to recreate the state even though there are no issues with the aggregation. We identified a possible root cause at the code level, and we need to fix it.
Steps to Reproduce
This issue reproduces when there is a large amount of data for aggregation. The Analytics server tries to load the AGG_TIMESTAMPS of each granularity and recreate them during the restart, even though there are no issues. If there is a high volume of data, it leads to an Out Of Memory (OOM) state.
Affected Component
Analytics
Version
3.2.0
Environment Details (with versions)
No response
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
wso2am-analytics-3.2.0
The text was updated successfully, but these errors were encountered:
Description
Hi Team,
There is high memory usage during the APIM Analytics server restart. During the investigation, we found that this issue occurs because the analytics server tries to recreate the state even though there are no issues with the aggregation. We identified a possible root cause at the code level, and we need to fix it.
Steps to Reproduce
This issue reproduces when there is a large amount of data for aggregation. The Analytics server tries to load the AGG_TIMESTAMPS of each granularity and recreate them during the restart, even though there are no issues. If there is a high volume of data, it leads to an Out Of Memory (OOM) state.
Affected Component
Analytics
Version
3.2.0
Environment Details (with versions)
No response
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
wso2am-analytics-3.2.0
The text was updated successfully, but these errors were encountered: