Repository navigation
Replies: 6 comments 6 replies
|
If you want to discuss about OOM, at least you should provide the result memory analysis. Otherwise, what do you expect from the community? |
|
OAP server has performance improvement in every release of 8.x, so what version do you use, how you use, what your memory dump looks like are the basic context you need to provide |
|
As I mentioned in my discussion, version 8.4.0 is used.Consume Kafka and write it to ES7. |
|
Two pieces of memory data are dumped every two minutes after startup. The comparison shows that the number of ServiceInstanceRelationClientCpmMetrics instances increases by 64319. |
|
|
|
Do you have any suggestions or solutions for this situation? Thank you. |
|
First of all, I would like to ask you to upgrade to 8.8.1. The change logs between 8.4.0 and 8.8.1, could show you that we improve a lot about data persistence. You could check whether this could help you. In another hand, if there is no leak(if you have verified GC and low load help), increasing memory to avoid full GC and OOM is important. We have seen users set memory to 20G to keep the performance high enough. |
|
Okay, thank you very much. |
|
|
|
|
|
|
|
The instance have been on the gc, after running for two or three minutes. |
Uh oh!
There was an error while loading. Please reload this page.
Search before asking
Apache SkyWalking Component
OAP server (apache/skywalking)
What happened
After the OAP is started for a while, the instance is abnormal and the error java.lang.OutOfMemoryError: GC overhead limit exceeded is reported. The VM memory is 8 GB. The JVM memory of the Docker container is set to 5 GB, and it could not be fixed.
What you expected to happen
The OAP can be normally started and written to the ES.
How to reproduce
Version 8.4.0 used
Anything else
No response
Are you willing to submit PR?
Code of Conduct
All reactions