We ran into this issue as well. Our ELB was from Amazon's EC2, which has a
known disconnect window. We overcame the issue by removing the ELB and
just using the ES Transport Client, which kind of acts like an ELB if you
think about it.
Cheers
On Monday, April 22, 2013 4:09:55 PM UTC-7, pm wrote:
We have simple test setup in a 2 cluster node with ELB in ec2 environment
(0.20.5). Running a simple script to index few documents in Elasticsearch
using ELB run intoException in thread "main" org.elasticsearch.client.transport.NoNodeAvailableException:
No node available
at org.elasticsearch.client.transport.TransportClientNodesService$
RetryListener.onFailure(TransportClientNodesService.java:246)
at org.elasticsearch.client.transport.TransportClientNodesService.
execute(TransportClientNodesService.java:214)
at org.elasticsearch.client.transport.support.
InternalTransportClient.execute(InternalTransportClient.java:106)
at org.elasticsearch.client.support.AbstractClient.update(
AbstractClient.java:105)
at org.elasticsearch.client.transport.TransportClient.
update(TransportClient.java:318)
at org.elasticsearch.action.update.UpdateRequestBuilder.doExecute(
UpdateRequestBuilder.java:298)
at org.elasticsearch.action.ActionRequestBuilder.execute(
ActionRequestBuilder.java:62)
at org.elasticsearch.action.ActionRequestBuilder.execute(
ActionRequestBuilder.java:57)However there is no problem so far running against the individual nodes. I
am using simple transport clientImmutableSettings.Builder elasticsearchSettings =
ImmutableSettings.settingsBuilder().put("cluster.name",
options.getEsCluster());
TransportClient client = new TransportClient(elasticsearchSettings);thanks
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.