We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The memory allocated for OrientDB is 8GB, and Hazelcast seems to be using almost 7.5GB.
vocations.percentage=0.00%, proxy.count=16, clientEndpoint.count=0, connection.active.count=0, client.connection.count=0, connection.count=0 [HealthMonitor]Exception in thread "OrientDB WAL Flush Task (authorization)" java.lang.OutOfMemoryError: GC overhead limit exceeded java.lang.OutOfMemoryError: GC overhead limit exceeded java.lang.OutOfMemoryError: GC overhead limit exceeded java.lang.OutOfMemoryError: GC overhead limit exceeded java.lang.OutOfMemoryError: GC overhead limit exceeded Error on client connection java.lang.OutOfMemoryError: GC overhead limit exceeded java.lang.OutOfMemoryError: GC overhead limit exceeded java.lang.OutOfMemoryError: GC overhead limit exceeded Error executing request com.orientechnologies.common.io.OIOException: Found unknown session 3407 at com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.onBeforeRequest(ONetworkProtocolBinary.java:240) at com.orientechnologies.orient.server.network.protocol.binary.OBinaryNetworkProtocolAbstract.execute(OBinaryNetworkProtocolAbstract.java:214) at com.orientechnologies.common.thread.OSoftThread.run(OSoftThread.java:77) [odb1.qa.shared.clks-int.com]:2434 [orientdbqafailover] [3.5.3] Failed to run java.lang.OutOfMemoryError: GC overhead limit exceeded Exception in thread "OrientDB WAL Flush Task (GratefulDeadConcerts)" java.lang.OutOfMemoryError: GC overhead limit exceeded Error on client connection
The text was updated successfully, but these errors were encountered:
Reopened in Support Platform
Sorry, something went wrong.
fixes of low disk check backported to 2.1.x, prjhub issue orientechno…
0f6f36c
…logies#6621
No branches or pull requests
Issue Observed
The memory allocated for OrientDB is 8GB, and Hazelcast seems to be using almost 7.5GB.
Exception thrown
vocations.percentage=0.00%, proxy.count=16, clientEndpoint.count=0, connection.active.count=0, client.connection.count=0, connection.count=0 [HealthMonitor]Exception in thread "OrientDB WAL Flush Task (authorization)" java.lang.OutOfMemoryError: GC overhead limit exceeded
java.lang.OutOfMemoryError: GC overhead limit exceeded
java.lang.OutOfMemoryError: GC overhead limit exceeded
java.lang.OutOfMemoryError: GC overhead limit exceeded
java.lang.OutOfMemoryError: GC overhead limit exceeded
Error on client connection
java.lang.OutOfMemoryError: GC overhead limit exceeded
java.lang.OutOfMemoryError: GC overhead limit exceeded
java.lang.OutOfMemoryError: GC overhead limit exceeded
Error executing request
com.orientechnologies.common.io.OIOException: Found unknown session 3407
at com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.onBeforeRequest(ONetworkProtocolBinary.java:240)
at com.orientechnologies.orient.server.network.protocol.binary.OBinaryNetworkProtocolAbstract.execute(OBinaryNetworkProtocolAbstract.java:214)
at com.orientechnologies.common.thread.OSoftThread.run(OSoftThread.java:77)
[odb1.qa.shared.clks-int.com]:2434 [orientdbqafailover] [3.5.3] Failed to run
java.lang.OutOfMemoryError: GC overhead limit exceeded
Exception in thread "OrientDB WAL Flush Task (GratefulDeadConcerts)" java.lang.OutOfMemoryError: GC overhead limit exceeded
Error on client connection
The text was updated successfully, but these errors were encountered: