Major Customer tends to get below ERROR in the nexus.log many times.
2020-09-22 00:31:12,254+0100 ERROR [OrientDB (/10.29.40.110:2424) <- BinaryClient (/10.29.40.110:45010)] gbrpsr000010801 *SYSTEM com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary - Error executing request
com.orientechnologies.common.io.OIOException: Impossible to read a chunk of length:16777315 max allowed chunk length:16777216 see NETWORK_BINARY_MAX_CONTENT_LENGTH settings
at com.orientechnologies.orient.enterprise.channel.binary.OChannelBinary.readBytes(OChannelBinary.java:160)
at com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.onBeforeOperationalRequest(ONetworkProtocolBinary.java:492)
at com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.sessionRequest(ONetworkProtocolBinary.java:365)
at com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.execute(ONetworkProtocolBinary.java:218)
at com.orientechnologies.common.thread.OSoftThread.run(OSoftThread.java:82)
Is this ERROR ignorable?
If not ignorable, I saw DatabaseServerImpl DEBUG logging shows below.
+ network.binary.maxLength = 16384
Would it be OK to increase OrientDB's property? Any side-effect?
This JIRA issue is to track the work to add a nexus property, "nexus.orient.network.binary.maxLengthKB" that allows us to configure the orient property.
This may alleviate this part of the customer problem.
Hajime
