mysql和OceanBase是社区双向数据同步,采用OMS

mysql和OceanBase是社区双向数据同步,采用OMS,跑了一段时间,出现了同步失败,

[2026-03-26 15:04:03.421] [WARN] [MySQLBinlogDumper(Netty)-I/O-0#0] An exception occurred on channel([id: 0x3d80f446, L:/10.100.10.239:49230 - R:/10.100.10.86:23306]) which has closed and nothing to do
618 io.netty.util.internal.OutOfDirectMemoryError: failed to allocate 1010827264 byte(s) of direct memory (used: 1035993088, max: 2040135680)
619 at io.netty.util.internal.PlatformDependent.incrementMemoryCounter(PlatformDependent.java:845)
620 at io.netty.util.internal.PlatformDependent.allocateDirectNoCleaner(PlatformDependent.java:774)
621 at io.netty.buffer.PoolArena$DirectArena.allocateDirect(PoolArena.java:701)
622 at io.netty.buffer.PoolArena$DirectArena.newUnpooledChunk(PoolArena.java:690)
623 at io.netty.buffer.PoolArena.allocateHuge(PoolArena.java:226)
624 at io.netty.buffer.PoolArena.allocate(PoolArena.java:144)
625 at io.netty.buffer.PoolArena.reallocate(PoolArena.java:302)
626 at io.netty.buffer.PooledByteBuf.capacity(PooledByteBuf.java:123)
627 at io.netty.buffer.AbstractByteBuf.ensureWritable0(AbstractByteBuf.java:305)
628 at io.netty.buffer.AbstractByteBuf.ensureWritable(AbstractByteBuf.java:280)
629 at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1103)
630 at io.netty.handler.codec.ByteToMessageDecoder$1.cumulate(ByteToMessageDecoder.java:105)
631 at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:288)
632 at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444)
633 at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
634 at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)
635 at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)
636 at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:440)
637 at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
638 at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)
639 at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:166)
640 at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:788)
641 at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724)
642 at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650)
643 at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562)
644 at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
645 at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
646 at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
647 at java.lang.Thread.run(Thread.java:853)

报内存溢出

官方大佬,帮忙看看叻?这个怎么处理叻?

store组件多分配点内存试试。

请问下在哪里,能调整这个参数吗?

image
找到参数调整大点
liboblog.memory_limit

我点开里面没有这一项叻

没有就新增

有,但是怎么知道以前是多大叻,另外请问下liboblog.memory_limit的单位是KB还是B叻

看你报错现在是2g,你调整为4g试试。可以加单位的



修改了还是没启动起来,下面是store.log日志,大佬帮看看啥原因叻
text (1).log (234.0 KB)

没看到最新的日志。不行你克隆下任务,注意位点时间。


在新增一個这个组件吗?

这样也可以。任务克隆也行