Open MobileAppVault opened 8 years ago
same issue still existent in 2.3.3
same issue in 2.3.0, in debug model , i found the error below: [2016-08-04 15:45:01,476][DEBUG][client.transport ] [Dionysus] node_sampler_interval[5s] [2016-08-04 15:45:01,493][DEBUG][org.xbib.elasticsearch.common.GcMonitor] enabled [true], interval [1s], gcthreshold [{default=GcThreshold{name='default', warnThreshold=10000, infoThreshold=5000, debugThreshold=2000}, young=GcThreshold{name='young', warnThreshold=1000, infoThreshold=700, debugThreshold=400}, old=GcThreshold{name='old', warnThreshold=10000, infoThreshold=5000, debugThreshold=2000}}] [2016-08-04 15:45:01,503][INFO ][org.xbib.elasticsearch.helper.client.BaseTransportClient] trying to connect to [192.168.10.4:9300] [2016-08-04 15:45:01,504][DEBUG][org.xbib.elasticsearch.helper.client.TransportClient] [Dionysus] adding address [{#transport#-1}{192.168.10.4}{192.168.10.4:9300}] [2016-08-04 15:45:01,504][DEBUG][org.xbib.elasticsearch.helper.client.TransportClient] [Dionysus] failed to connect to node [{#transport#-1}{192.168.10.4}{192.168.10.4:9300}], removed from nodes list ConnectTransportException[[][192.168.10.4:9300] general node connection failure]; nested: IllegalStateException[await() in I/O thread causes a dead lock or sudden performance drop. Use addListener() instead or call await() from a different thread.]; at org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:937) at org.elasticsearch.transport.netty.NettyTransport.connectToNodeLight(NettyTransport.java:888) at org.elasticsearch.transport.TransportService.connectToNodeLight(TransportService.java:267) at org.xbib.elasticsearch.helper.client.TransportClient.connect(TransportClient.java:348) at org.xbib.elasticsearch.helper.client.TransportClient.addTransportAddresses(TransportClient.java:281) at org.xbib.elasticsearch.helper.client.BaseTransportClient.connect(BaseTransportClient.java:98) at org.xbib.elasticsearch.helper.client.BulkTransportClient.init(BulkTransportClient.java:162) at org.xbib.elasticsearch.helper.client.ClientBuilder.toBulkTransportClient(ClientBuilder.java:112) at org.xbib.elasticsearch.action.knapsack.push.TransportKnapsackPushAction.doExecute(TransportKnapsackPushAction.java:101) at org.xbib.elasticsearch.action.knapsack.push.TransportKnapsackPushAction.doExecute(TransportKnapsackPushAction.java:66) at org.elasticsearch.action.support.TransportAction.doExecute(TransportAction.java:149) at org.elasticsearch.action.support.TransportAction.execute(TransportAction.java:137) at org.elasticsearch.action.support.TransportAction.execute(TransportAction.java:85) at org.elasticsearch.client.node.NodeClient.doExecute(NodeClient.java:58) at org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:359) at org.elasticsearch.client.FilterClient.doExecute(FilterClient.java:52) ....... at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.IllegalStateException: await() in I/O thread causes a dead lock or sudden performance drop. Use addListener() instead or call await_() from a different thread. at org.jboss.netty.channel.DefaultChannelFuture.checkDeadLock(DefaultChannelFuture.java:320) at org.jboss.netty.channel.DefaultChannelFuture.await0(DefaultChannelFuture.java:284) at org.jboss.netty.channel.DefaultChannelFuture.awaitUninterruptibly(DefaultChannelFuture.java:263) at org.elasticsearch.transport.netty.NettyTransport.connectToChannelsLight(NettyTransport.java:950) at org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:916) ... 63 more [2016-08-04 15:45:01,505][ERROR][KnapsackPushAction ] no cluster nodes available, check settings {client.transport.ignore_cluster_name=true, client.transport.ping_timeout=30s, client.transport.sniff=true, cluster.name=liveyc, flush_interval=5s, host=192.168.10.4, max_actions_per_request=1000, max_concurrent_requests=4, path.plugins=.dontexist, port=9300, timeout=30s} NoNodeAvailableException[no cluster nodes available, check settings {client.transport.ignore_cluster_name=true, client.transport.ping_timeout=30s, client.transport.sniff=true, cluster.name=liveyc, flush_interval=5s, host=192.168.10.4, max_actions_per_request=1000, max_concurrent_requests=4, path.plugins=.dontexist, port=9300, timeout=30s}] at org.xbib.elasticsearch.helper.client.BulkTransportClient.init(BulkTransportClient.java:164) at org.xbib.elasticsearch.helper.client.ClientBuilder.toBulkTransportClient(ClientBuilder.java:112) at org.xbib.elasticsearch.action.knapsack.push.TransportKnapsackPushAction.doExecute(TransportKnapsackPushAction.java:101) at org.xbib.elasticsearch.action.knapsack.push.TransportKnapsackPushAction.doExecute(TransportKnapsackPushAction.java:66) at org.elasticsearch.action.support.TransportAction.doExecute(TransportAction.java:149) at org.elasticsearch.action.support.TransportAction.execute(TransportAction.java:137) at org.elasticsearch.action.support.TransportAction.execute(TransportAction.java:85) at org.elasticsearch.client.node.NodeClient.doExecute(NodeClient.java:58) at org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:359)
Thanks. There are limitations in Elasticsearch, I can only think of fixing this by disabling Netty dead lock checking. Will be in next release #110
Hi,
I've tried to push indices from one cluster to another and got the following error.
I already checked my firewall settings and all firewalls deactivated and I checkt the transport ports and they are also available. The file export is working fine.
Could you please have a look into that issue?
Request
http://10.00.00.00:9200/products/_push?&host=10.00.00.13&port=9300&cluster=TEST
Response
Configuration
CLUSTER 1
CLUSTER 2
Elastic Version 2.3.1
Here is the log file: