No node available exception

Hi, I am using transport client for ES. I have a search request for 1 million records. I am getting No node available exception after getting 8k records itself. What can be done to overcome this issue? Its very urgent please help. Thanks. -- View this message in context: http

Re: No node available exception

When i set the ping timeout for transport client to a higher value, the issue is fixed automatically. -- View this message in context: http://elasticsearch-users.115913.n3.nabble.com/No-node-available-exception-tp4069387p4069408.html Sent from the ElasticSearch Users mailing list archive

Re: No node available Exception

We had the same problem. reason: The application server uses a older version of log4j than ES needed. Am Mittwoch, 4. Dezember 2013 19:31:26 UTC+1 schrieb Justin Uang: I get the same problem too. Our configuration has us using the TransportClient, and we have a single node cluster using the

no node available exception after node shutdown

Hi folks, we have a two node cluster and we connect to it using the TransportClient from java by adding two hosts, i.e. ((TransportClient) client).addTransportAddress(new InetSocketTransportAddress(elastic1, port)); ((TransportClient) client).addTransportAddress(new

getting no node available exception when there are many requests

Hello all, I'm using storm with elasticsearch percolator and normally it works as expected. but when there are to many requests simultaneously, some of them succeed and some fail with no node available exception. I think there should be a configuration about maximum requests per seconds

Re: TransportClient of ES 1.1.1 on Ubantu 12.x throws 'No node available' exception

But be aware that there is a bug in Elasticsearch which can cause the transport client to get the NoNodeAvailable exception of sniff is set to false. It doesn't seem to have been the issue in this case but I thought I should mention it. -- You received this message because you are subscribed

TransportClient of ES 1.1.1 on Ubantu 12.x throws 'No node available' exception

I have ugraded ES from 0.90.2 to ES 1.1.1 recently. I am able to get the Tranpsort client of ES 1.1.1 and create mapping on Windows 2010. But I get a 'No node available' exception on Ubantu 12.x Here is the code I use for connecting to ES ImmutableSettings.Builder settingsBuilder

Re: TransportClient of ES 1.1.1 on Ubantu 12.x throws 'No node available' exception

and create mapping on Windows 2010. But I get a 'No node available' exception on Ubantu 12.x Here is the code I use for connecting to ES ImmutableSettings.Builder settingsBuilder = ImmutableSettings.settingsBuilder(); // because default cluster name used //settingsBuilder.put

Re: TransportClient of ES 1.1.1 on Ubantu 12.x throws 'No node available' exception

read (request) for [0] and action [], resetting' On Wednesday, May 28, 2014 12:07:39 PM UTC+5:30, Chetana wrote: I have ugraded ES from 0.90.2 to ES 1.1.1 recently. I am able to get the Tranpsort client of ES 1.1.1 and create mapping on Windows 2010. But I get a 'No node available' exception

Getting 'No Node Available Exception' while using TrasnsportClient of ElasticSearch.

Hi, I am pretty new to Elastic Search. I have following things in my code OR looking for solution to 'No Node Available Exception' problem in the following scenario. 1) We have ES running on System with 1 Node and 1 Cluster 2) We have 4 indexes on ES. (Each index has different type of data

No Node available exception while connection to elasticsearch cluster

are connecting to each other perfectly, and i can create index, and ad data to it by using curl command. But when create connection through java program the i get a no node available exception. I am using following code for creating connection. Settings s = ImmutableSettings.settingsBuilder().put