Maybe force client to server connection or scale out your ignite cluster to reduce the number of connections on each node. Each connection needs buffer space of a multiple of the bandwidth delay product to keep data flowing without stuttering.
On Fri, Aug 18, 2023, 21:43 f cad <[email protected]> wrote: > Thanks for your suggestion > we set MaxDirectMemorySize to 8g,it still has exception. > we use spark to read ignite.and use ThinIgniteClientOnK8s api to read. > we find that if multiple spark applications read ignite, then ignite will > hit the direct buffer memory oom. > can you give me some suggestions about how can i confirm that it is a > network problem? > Best Regards. > > Jeremy McMillan <[email protected]> 于2023年8月18日周五 20:39写道： > >> This is most likely to happen when Ignite is fast and the network is >> slow. It's unclear what's happening when you experience this error, so how >> to fix it is also ambiguous. >> >> You could try increasing direct buffer memory in Java options. If that's >> not sufficient share more about your infrastructure and workload and maybe >> we can suggest something else. >> >> On Fri, Aug 18, 2023, 04:28 f cad <[email protected]> wrote: >> >>> hello, >>> in my ignite cluster.i meet error below: >>> JVM will be halted immediately due to the failure: >>> [failureCtx=FailureContext [type=CRITICAL_ERROR, >>> err=java.lang.OutOfMemoryError: Direct buffer memory]]. >>> how can i fix. >>> ignite version is 2.14 >>> >>
