带有RSS插件的elasticsearch在重启后挂起

时间:2015-01-14 07:49:48

标签: java elasticsearch elasticsearch-plugin elasticsearch-jdbc-river

我的Mac上有一个带有RSS插件的干净ES服务器 - 添加几个源后服务器在重新启动后挂起(因为我想添加额外的插件或重新启动mac)。

有没有办法阻止它/恢复当前安装?

日志:

  

[2015-01-14 09:43:27,870] [警告] [discovery.zen.ping.multicast]   [Mar-Vell]收到ping响应ping_response {node   [[阿斯莫德] [JpUdhq0FRYKr7RqDqcK7WQ] [Dorons-MBP.Home] [INET [/10.0.0.7:9300]]],   id [1089],主人   [[阿斯莫德] [JpUdhq0FRYKr7RqDqcK7WQ] [Dorons-MBP.Home] [INET [/10.0.0.7:9300]]],   hasJoinedOnce [true],cluster_name [elasticsearch]}没有匹配的id   [2] [2015-01-14 09:43:30,724] [DEBUG] [action.admin.cluster.health]   [Mar-Vell]没有已知的主节点,安排重试[2015-01-14   09:43:57,943] [警告] [discovery.zen] [Mar-Vell]未能成功   连接到主人   [[阿斯莫德] [JpUdhq0FRYKr7RqDqcK7WQ] [Dorons-MBP.Home] [INET [/10.0.0.7:9300]]],   正在重试... org.elasticsearch.transport.ConnectTransportException:   [Asmodeus] [inet [/10.0.0.7:9300]] connect_timeout [30s] at   org.elasticsearch.transport.netty.NettyTransport.connectToChannels(NettyTransport.java:807)     在   org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:741)     在   org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:714)     在   org.elasticsearch.transport.TransportService.connectToNode(TransportService.java:150)     在   org.elasticsearch.discovery.zen.ZenDiscovery.joinElectedMaster(ZenDiscovery.java:441)     在   org.elasticsearch.discovery.zen.ZenDiscovery.innerJoinCluster(ZenDiscovery.java:393)     在   org.elasticsearch.discovery.zen.ZenDiscovery.access $ 6000(ZenDiscovery.java:80)     在   org.elasticsearch.discovery.zen.ZenDiscovery $ JoinThreadControl $ 1.run(ZenDiscovery.java:1318)     在   java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)     在   java.util.concurrent.ThreadPoolExecutor中的$ Worker.run(ThreadPoolExecutor.java:615)     在java.lang.Thread.run(Thread.java:744)引起:   org.elasticsearch.common.netty.channel.ConnectTimeoutException:   连接超时:/10.0.0.7:9300 at   org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processConnectTimeout(NioClientBoss.java:139)     在   org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:83)     在   org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:318)     在   org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)     在   org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)     在   org.elasticsearch.common.netty.util.internal.DeadLockProofWorker $ 1.run(DeadLockProofWorker.java:42)     ... 3更多[2015-01-14   09:44:00,729] [DEBUG] [action.admin.cluster.health] [Mar-Vell]观察员:   群集服务的超时通知。超时设置[30s],时间   从开始[30s] [2015-01-14 09:44:01,048] [警告   ] [discovery.zen.ping.multicast] [Mar-Vell]收到ping响应   ping_response {节点   [[阿斯莫德] [JpUdhq0FRYKr7RqDqcK7WQ] [Dorons-MBP.Home] [INET [/10.0.0.7:9300]]],   id [1095],主人   [[阿斯莫德] [JpUdhq0FRYKr7RqDqcK7WQ] [Dorons-MBP.Home] [INET [/10.0.0.7:9300]]],   hasJoinedOnce [true],cluster_name [elasticsearch]}没有匹配的id   [3]

0 个答案:

没有答案