开发者社区> 问答> 正文

otter运行过程中,同步节点2088端口报未启动,但是同步进程还存在

otter运行过程中,同步节点2088端口报未启动,但是同步进程还存在,需要重启同步程序即可。 MYSQL 5.6.26 otter 4.2.12

#380 这个链接涉及到的报错java.lang.OutOfMemoryError: Java heap space 已经没有了,但还是每个一周左右的样子还是会出现2088端口没启动的报错

日志如下: 2018-03-04 06:33:05.466 [DubboServerHandler-127.0.0.1:2088-thread-49] WARN c.a.o.shared.arbitrate.impl.setl.monitor.Main stemMonitor - mainstem is not run any in node 2018-03-04 06:33:05.466 [Arbitrate-Monitor-0] ERROR c.a.o.shared.arbitrate.impl.setl.monitor.PermitMonitor - /otter/chann el/3/10/mainstem org.I0Itec.zkclient.exception.ZkInterruptedException: java.lang.InterruptedException at com.alibaba.otter.shared.common.utils.zookeeper.ZkClientx.retryUntilConnected(ZkClientx.java:787) ~[shared.com mon-4.2.12.jar:na] at com.alibaba.otter.shared.common.utils.zookeeper.ZkClientx.readData(ZkClientx.java:866) ~[shared.common-4.2.12. jar:na] at com.alibaba.otter.shared.common.utils.zookeeper.ZkClientx.readData(ZkClientx.java:861) ~[shared.common-4.2.12. jar:na] at com.alibaba.otter.shared.common.utils.zookeeper.ZkClientx.readData(ZkClientx.java:850) ~[shared.common-4.2.12. jar:na] at com.alibaba.otter.shared.common.utils.zookeeper.ZkClientx.readData(ZkClientx.java:844) ~[shared.common-4.2.12. jar:na] at com.alibaba.otter.shared.arbitrate.impl.setl.monitor.PermitMonitor.initMainStemStatus(PermitMonitor.java:329) [shared.arbitrate-4.2.12.jar:na] at com.alibaba.otter.shared.arbitrate.impl.setl.monitor.PermitMonitor.reload(PermitMonitor.java:144) [shared.arbi trate-4.2.12.jar:na] at com.alibaba.otter.shared.arbitrate.impl.setl.monitor.MonitorScheduler$1.run(MonitorScheduler.java:74) [shared. arbitrate-4.2.12.jar:na] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [na:1.7.0_45] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) [na:1.7.0_45] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.ja va:178) [na:1.7.0_45] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [na:1.7.0_45] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_45] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_45] at java.lang.Thread.run(Thread.java:744) [na:1.7.0_45] Caused by: java.lang.InterruptedException: null at java.lang.Object.wait(Native Method) ~[na:1.7.0_45] at java.lang.Object.wait(Object.java:503) ~[na:1.7.0_45] at org.apache.zookeeper.ClientCnxn.submitRequest(ClientCnxn.java:1309) ~[zookeeper-3.4.5.jar:3.4.5-1392090] at org.apache.zookeeper.ZooKeeper.getData(ZooKeeper.java:1149) ~[zookeeper-3.4.5.jar:3.4.5-1392090] at org.apache.zookeeper.ZooKeeper.getData(ZooKeeper.java:1180) ~[zookeeper-3.4.5.jar:3.4.5-1392090] at com.alibaba.otter.shared.common.utils.zookeeper.ZooKeeperx.readData(ZooKeeperx.java:127) ~[shared.common-4.2.1 2.jar:na] at com.alibaba.otter.shared.common.utils.zookeeper.ZkClientx$10.call(ZkClientx.java:870) ~[shared.common-4.2.12.j ar:na] at com.alibaba.otter.shared.common.utils.zookeeper.ZkClientx$10.call(ZkClientx.java:866) ~[shared.common-4.2.12.j ar:na] at com.alibaba.otter.shared.common.utils.zookeeper.ZkClientx.retryUntilConnected(ZkClientx.java:775) ~[shared.com mon-4.2.12.jar:na] ... 14 common frames omitted 2018-03-04 06:33:05.467 [Arbitrate-Monitor-0] ERROR c.a.o.shared.arbitrate.impl.setl.monitor.PermitMonitor - /otter/chann el/3/5/mainstem org.I0Itec.zkclient.exception.ZkInterruptedException: java.lang.InterruptedException at com.alibaba.otter.shared.common.utils.zookeeper.ZkClientx.retryUntilConnected(ZkClientx.java:787) ~[shared.com mon-4.2.12.jar:na] at com.alibaba.otter.shared.common.utils.zookeeper.ZkClientx.readData(ZkClientx.java:866) ~[shared.common-4.2.12. jar:na] at com.alibaba.otter.shared.common.utils.zookeeper.ZkClientx.readData(ZkClientx.java:861) ~[shared.common-4.2.12. jar:na] at com.alibaba.otter.shared.common.utils.zookeeper.ZkClientx.readData(ZkClientx.java:850) ~[shared.common-4.2.12. jar:na] at com.alibaba.otter.shared.common.utils.zookeeper.ZkClientx.readData(ZkClientx.java:844) ~[shared.common-4.2.12. jar:na] at com.alibaba.otter.shared.arbitrate.impl.setl.monitor.PermitMonitor.initOppositeMainStemStatus(PermitMonitor.ja va:393) [shared.arbitrate-4.2.12.jar:na] at com.alibaba.otter.shared.arbitrate.impl.setl.monitor.PermitMonitor.reload(PermitMonitor.java:158) [shared.arbi trate-4.2.12.jar:na] at com.alibaba.otter.shared.arbitrate.impl.setl.monitor.MonitorScheduler$1.run(MonitorScheduler.java:74) [shared. arbitrate-4.2.12.jar:na] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [na:1.7.0_45] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) [na:1.7.0_45] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.ja va:178) [na:1.7.0_45] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [na:1.7.0_45] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_45] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_45] at java.lang.Thread.run(Thread.java:744) [na:1.7.0_45] Caused by: java.lang.InterruptedException: null at java.lang.Object.wait(Native Method) ~[na:1.7.0_45] at java.lang.Object.wait(Object.java:503) ~[na:1.7.0_45] at org.apache.zookeeper.ClientCnxn.submitRequest(ClientCnxn.java:1309) ~[zookeeper-3.4.5.jar:3.4.5-1392090] at org.apache.zookeeper.ZooKeeper.getData(ZooKeeper.java:1149) ~[zookeeper-3.4.5.jar:3.4.5-1392090] at org.apache.zookeeper.ZooKeeper.getData(ZooKeeper.java:1180) ~[zookeeper-3.4.5.jar:3.4.5-1392090] at com.alibaba.otter.shared.common.utils.zookeeper.ZooKeeperx.readData(ZooKeeperx.java:127) ~[shared.common-4.2.1 2.jar:na] at com.alibaba.otter.shared.common.utils.zookeeper.ZkClientx$10.call(ZkClientx.java:870) ~[shared.common-4.2.12.j ar:na] at com.alibaba.otter.shared.common.utils.zookeeper.ZkClientx$10.call(ZkClientx.java:866) ~[shared.common-4.2.12.j ar:na] at com.alibaba.otter.shared.common.utils.zookeeper.ZkClientx.retryUntilConnected(ZkClientx.java:775) ~[shared.com mon-4.2.12.jar:na] ... 14 common frames omitted 2018-03-04 06:33:06.611 [DubboServerHandler-127.0.0.1:2088-thread-49] WARN c.a.o.shared.arbitrate.impl.setl.monitor.Main stemMonitor - mainstem is not run any in node 2018-03-04 06:37:05.625 [DubboServerHandler-127.0.0.1:2088-thread-49] WARN c.a.o.shared.arbitrate.impl.setl.monitor.Main stemMonitor - mainstem is not run any in node 2018-03-04 06:37:06.775 [DubboServerHandler-127.0.0.1:2088-thread-49] WARN c.a.o.shared.arbitrate.impl.setl.monitor.Main stemMonitor - mainstem is not run any in node 2018-03-04 06:39:05.675 [DubboServerHandler-127.0.0.1:2088-thread-49] WARN c.a.o.shared.arbitrate.impl.setl.monitor.Main stemMonitor - mainstem is not run any in node 2018-03-04 06:39:06.834 [DubboServerHandler-127.0.0.1:2088-thread-49] WARN c.a.o.shared.arbitrate.impl.setl.monitor.Main stemMonitor - mainstem is not run any in node 2018-03-04 06:41:05.769 [DubboServerHandler-127.0.0.1:2088-thread-49] WARN c.a.o.shared.arbitrate.impl.setl.monitor.Main stemMonitor - mainstem is not run any in node 2018-03-04 06:41:06.924 [DubboServerHandler-127.0.0.1:2088-thread-49] WARN c.a.o.shared.arbitrate.impl.setl.monitor.Main stemMonitor - mainstem is not run any in node

2018-03-04 13:57:25.196 [DubboServerHandler-127.0.0.1:2088-thread-49] WARN c.a.o.shared.arbitrate.impl.setl.monitor.Main stemMonitor - mainstem is not run any in node 2018-03-04 13:59:23.673 [DubboServerHandler-127.0.0.1:2088-thread-49] WARN c.a.o.shared.arbitrate.impl.setl.monitor.Main stemMonitor - mainstem is not run any in node 2018-03-04 13:59:24.819 [DubboServerHandler-127.0.0.1:2088-thread-49] WARN c.a.o.shared.arbitrate.impl.setl.monitor.Main stemMonitor - mainstem is not run any in node 2018-03-04 14:01:24.199 [DubboServerHandler-127.0.0.1:2088-thread-49] WARN c.a.o.shared.arbitrate.impl.setl.monitor.Main stemMonitor - mainstem is not run any in node 2018-03-04 14:01:25.531 [DubboServerHandler-127.0.0.1:2088-thread-49] WARN c.a.o.shared.arbitrate.impl.setl.monitor.Main stemMonitor - mainstem is not run any in node 2018-03-04 14:07:23.931 [DubboServerHandler-127.0.0.1:2088-thread-49] WARN c.a.o.shared.arbitrate.impl.setl.monitor.Main stemMonitor - mainstem is not run any in node 2018-03-04 14:09:24.026 [DubboServerHandler-127.0.0.1:2088-thread-49] WARN c.a.o.shared.arbitrate.impl.setl.monitor.Main stemMonitor - mainstem is not run any in node 2018-03-04 14:09:25.170 [DubboServerHandler-127.0.0.1:2088-thread-49] WARN c.a.o.shared.arbitrate.impl.setl.monitor.Main stemMonitor - mainstem is not run any in node 2018-03-04 14:11:24.112 [DubboServerHandler-127.0.0.1:2088-thread-49] WARN c.a.o.shared.arbitrate.impl.setl.monitor.Main stemMonitor - mainstem is not run any in node 2018-03-04 14:11:25.714 [DubboServerHandler-127.0.0.1:2088-thread-49] WARN c.a.o.shared.arbitrate.impl.setl.monitor.Main stemMonitor - mainstem is not run any in node 2018-03-04 14:15:24.795 [DubboServerHandler-127.0.0.1:2088-thread-49] WARN c.a.o.shared.arbitrate.impl.setl.monitor.Main stemMonitor - mainstem is not run any in node 2018-03-04 14:15:26.271 [DubboServerHandler-127.0.0.1:2088-thread-49] WARN c.a.o.shared.arbitrate.impl.setl.monitor.Main stemMonitor - mainstem is not run any in node 2018-03-04 17:44:36.974 [dubbo-remoting-server-heartbeat-thread-1] WARN c.a.dubbo.remoting.exchange.support.header.Heart BeatTask - [DUBBO] Close channel NettyChannel [channel=[id: 0x3107f8ff, /172.21.35.139:33502 => /172.21.79.34:2088]], be cause heartbeat read idle time out: 15000ms, dubbo version: 2.5.3, current host: 127.0.0.1 2018-03-04 20:39:03.263 [dubbo-remoting-client-heartbeat-thread-2] WARN c.a.dubbo.remoting.exchange.support.header.Heart BeatTask - [DUBBO] Close channel HeaderExchangeClient [channel=com.alibaba.dubbo.remoting.transport.netty.NettyClient [/ 172.21.77.34:49088 -> /172.21.46.139:1099]], because heartbeat read idle time out: 180000ms, dubbo version: 2.5.3, curren t host: 127.0.0.1

原提问者GitHub用户 aiaix

展开
收起
古拉古拉 2023-06-18 10:47:11 76 0
1 条回答
写回答
取消 提交回答
  • 重启一下node吧

    原回答者GitHub用户 agapple

    2023-06-18 11:04:11
    赞同 展开评论 打赏
问答排行榜
最热
最新

相关电子书

更多
服务上云加速大家居产业C2M进程 立即下载
低代码开发师(初级)实战教程 立即下载
阿里巴巴DevOps 最佳实践手册 立即下载

相关实验场景

更多