otter 双向同步主站点点位更新但不同步

bgtovc5b  于 3个月前  发布在  其他
关注(0)|答案(4)|浏览(73)

有中国节点和新加坡节点,其中以中国节点主节点建立双向channel,新加坡 -> 中国同步正常,但中国节点不同步到新加坡,控制台可以看到点位信息不断更新,但是最后同步时间为空。

以下是新加坡node日志:

2017-11-13 06:42:18.627 [DubboClientReconnectTimer-thread-1] WARN  com.alibaba.dubbo.remoting.transport.AbstractClient -  [DUBBO] client reconnect to xxxxxxxxxx:2088 find error . url: dubbo://xxxxxxxx:2088/endpoint?acceptEvent.timeout=50000&client=netty&codec=dubbo&connections=30&heartbeat=60000&iothreads=4&lazy=true&send.reconnect=true&serialization=java&threads=50, dubbo version: 2.5.3, current host: xxxxx
		com.alibaba.dubbo.remoting.RemotingException: client(url: dubbo://xxxxxxxxxx:2088/endpoint?acceptEvent.timeout=50000&client=netty&codec=dubbo&connections=30&heartbeat=60000&iothreads=4&lazy=true&send.reconnect=true&serialization=java&threads=50) failed to connect to server /xxxxxxxxxxxx:2088, error message is:connection timed out
		at com.alibaba.dubbo.remoting.transport.netty.NettyClient.doConnect(NettyClient.java:124) ~[dubbo-2.5.3.jar:2.5.3]
		at com.alibaba.dubbo.remoting.transport.AbstractClient.connect(AbstractClient.java:280) ~[dubbo-2.5.3.jar:2.5.3]
		at com.alibaba.dubbo.remoting.transport.AbstractClient$1.run(AbstractClient.java:145) ~[dubbo-2.5.3.jar:2.5.3]
		at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_151]
		at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [na:1.8.0_151]
		at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_151]
		at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [na:1.8.0_151]
		at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_151]
		at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_151]
		at java.lang.Thread.run(Thread.java:748) [na:1.8.0_151]
		Caused by: java.net.ConnectException: connection timed out
		at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.processConnectTimeout(NioClientSocketPipelineSink.java:371) ~[netty-3.2.2.Final.jar:na]
		at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.run(NioClientSocketPipelineSink.java:283) ~[netty-3.2.2.Final.jar:na]
		at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) ~[netty-3.2.2.Final.jar:na]
		at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46) ~[netty-3.2.2.Final.jar:na]
		... 3 common frames omitted
		2017-11-13 06:42:47.219 [dubbo-remoting-server-heartbeat-thread-1] WARN  c.a.dubbo.remoting.exchange.support.header.HeartBeatTask -  [DUBBO] Close channel NettyChannel [channel=[id: 0x16796b5a, /xxxxxxxxx:34506 => /xxxxxxxxx:2088]], because heartbeat read idle time out: 15000ms, dubbo version: 2.5.3, current host: xxxxxx
2017-11-13 06:42:18.627 [DubboClientReconnectTimer-thread-1] WARN  com.alibaba.dubbo.remoting.transport.AbstractClient -  [DUBBO] client reconnect to xxxxxxxxxx:2088 find error . url: dubbo://xxxxxxxx:2088/endpoint?acceptEvent.timeout=50000&client=netty&codec=dubbo&connections=30&heartbeat=60000&iothreads=4&lazy=true&send.reconnect=true&serialization=java&threads=50, dubbo version: 2.5.3, current host: xxxxxx
		com.alibaba.dubbo.remoting.RemotingException: client(url: dubbo://xxxxxxxxxx:2088/endpoint?acceptEvent.timeout=50000&client=netty&codec=dubbo&connections=30&heartbeat=60000&iothreads=4&lazy=true&send.reconnect=true&serialization=java&threads=50) failed to connect to server /xxxxxxxxxxxx:2088, error message is:connection timed out
		at com.alibaba.dubbo.remoting.transport.netty.NettyClient.doConnect(NettyClient.java:124) ~[dubbo-2.5.3.jar:2.5.3]
		at com.alibaba.dubbo.remoting.transport.AbstractClient.connect(AbstractClient.java:280) ~[dubbo-2.5.3.jar:2.5.3]
		at com.alibaba.dubbo.remoting.transport.AbstractClient$1.run(AbstractClient.java:145) ~[dubbo-2.5.3.jar:2.5.3]
		at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_151]
		at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [na:1.8.0_151]
		at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_151]
		at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [na:1.8.0_151]
		at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_151]
		at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_151]
		at java.lang.Thread.run(Thread.java:748) [na:1.8.0_151]
		Caused by: java.net.ConnectException: connection timed out
		at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.processConnectTimeout(NioClientSocketPipelineSink.java:371) ~[netty-3.2.2.Final.jar:na]
		at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.run(NioClientSocketPipelineSink.java:283) ~[netty-3.2.2.Final.jar:na]
		at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) ~[netty-3.2.2.Final.jar:na]
		at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46) ~[netty-3.2.2.Final.jar:na]
		... 3 common frames omitted
		2017-11-13 06:42:47.219 [dubbo-remoting-server-heartbeat-thread-1] WARN  c.a.dubbo.remoting.exchange.support.header.HeartBeatTask -  [DUBBO] Close channel NettyChannel [channel=[id: 0x16796b5a, /xxxxxxxxx:34506 => /xxxxxxxx:2088]], because heartbeat read idle time out: 15000ms, dubbo version: 2.5.3, current host: xxxxxxx
yyyllmsg

yyyllmsg1#

我也遇到了同样的问题
pid:1 nid:2 exception:setl:com.alibaba.otter.shared.communication.core.exception.CommunicationException: call[192.168.48.46:2088] , Event[AbstractRpcPipe.RpcEvent[key=RpcPipeKey[nid=1,identity=Identity[channelId=1,pipelineId=1,processId=120],time=1521867038806,dataType=DB_BATCH],type=get]] Caused by: com.alibaba.dubbo.rpc.RpcException: Failed to invoke remote method: acceptEvent, provider: dubbo://192.168.48.46:2088/endpoint?acceptEvent.timeout=50000&client=netty&codec=dubbo&connections=30&iothreads=4&lazy=true&serialization=java&threads=50, cause: client(url: dubbo://192.168.48.46:2088/endpoint?acceptEvent.timeout=50000&client=netty&codec=dubbo&connections=30&heartbeat=60000&iothreads=4&lazy=true&send.reconnect=true&serialization=java&threads=50) failed to connect to server /192.168.48.46:2088, error message is:connection timed out at com.alibaba.dubbo.rpc.protocol.dubbo.DubboInvoker.doInvoke(DubboInvoker.java:101) at com.alibaba.dubbo.rpc.protocol.AbstractInvoker.invoke(AbstractInvoker.java:144) at com.alibaba.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerInvocationHandler.java:52) at com.alibaba.dubbo.common.bytecode.proxy1.acceptEvent(proxy1.java) at com.alibaba.otter.shared.communication.core.impl.dubbo.DubboCommunicationConnection.call(DubboCommunicationConnection.java:45) at com.alibaba.otter.shared.communication.core.impl.DefaultCommunicationClientImpl.call(DefaultCommunicationClientImpl.java:96) at com.alibaba.otter.node.common.communication.NodeCommmunicationClient.call(NodeCommmunicationClient.java:51) at com.alibaba.otter.node.etl.common.pipe.impl.rpc.RowDataRpcPipe.get(RowDataRpcPipe.java:60) at com.alibaba.otter.node.etl.common.pipe.impl.RowDataPipeDelegate.get(RowDataPipeDelegate.java:146) at com.alibaba.otter.node.etl.transform.TransformTask$1.run(TransformTask.java:76) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: com.alibaba.dubbo.remoting.RemotingException: client(url: dubbo://192.168.48.46:2088/endpoint?acceptEvent.timeout=50000&client=netty&codec=dubbo&connections=30&heartbeat=60000&iothreads=4&lazy=true&send.reconnect=true&serialization=java&threads=50) failed to connect to server /192.168.48.46:2088, error message is:connection timed out at com.alibaba.dubbo.remoting.transport.netty.NettyClient.doConnect(NettyClient.java:124) at com.alibaba.dubbo.remoting.transport.AbstractClient.connect(AbstractClient.java:280) at com.alibaba.dubbo.remoting.transport.AbstractClient.(AbstractClient.java:103) at com.alibaba.dubbo.remoting.transport.netty.NettyClient.(NettyClient.java:61) at com.alibaba.dubbo.remoting.transport.netty.NettyTransporter.connect(NettyTransporter.java:37) at com.alibaba.dubbo.remoting.Transporter$Adpative.connect(Transporter$Adpative.java) at com.alibaba.dubbo.remoting.Transporters.connect(Transporters.java:67) at com.alibaba.dubbo.remoting.exchange.support.header.HeaderExchanger.connect(HeaderExchanger.java:37) at com.alibaba.dubbo.remoting.exchange.Exchangers.connect(Exchangers.java:102) at com.alibaba.dubbo.rpc.protocol.dubbo.LazyConnectExchangeClient.initClient(LazyConnectExchangeClient.java:79) at com.alibaba.dubbo.rpc.protocol.dubbo.LazyConnectExchangeClient.request(LazyConnectExchangeClient.java:104) at com.alibaba.dubbo.rpc.protocol.dubbo.DubboInvoker.doInvoke(DubboInvoker.java:96) ... 14 more Caused by: java.net.ConnectException: connection timed out at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.processConnectTimeout(NioClientSocketPipelineSink.java:371) at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.run(NioClientSocketPipelineSink.java:283) at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46) ... 3 more

hk8txs48

hk8txs482#

请问您的问题解决了吗?什么原因该如何处理能分享一下不?

5ktev3wc

5ktev3wc3#

@hphuangpu 过一段时间自己好的。

py49o6xq

py49o6xq4#

这也可以?我出过几回这个问题,是通过重启node机器恢复正常的。不知具体原因。

相关问题