Any news on this item, I'm having exactly the same problem. "No node
available" in the middle of indexing, hundreds of documents are processed
just fine, then at varying times I get this exception. I have played around
with giving ES (much) more memory, other GC settings, etc... the problem
persists though it's quite random when it occurs. One pattern I did notice
is that I usually get the following warning around the time when the
exception occurs:
[2013-05-22 18:10:09,631][WARN ][monitor.jvm ] [Inspector
Clouseau] [gc][PS MarkSweep][80682][26] duration [21.3s], collections
[1]/[21.9s
], total [21.3s]/[31s], memory [824.2mb]->[200.4mb]/[1.7gb], all_pools
{[Code Cache] [6.3mb]->[6.3mb]/[48mb]}{[PS Eden Space]
[189.5mb]->[573.9kb]/[569.5mb]}{[PS Survivor Space]
[20.8mb]->[0b]/[54.6mb]}{[PS Old Gen] [613.8mb]->[199.8mb]/[1.3gb]}{[PS
Perm Gen] [32.5mb]->[32.5mb]/[82mb]}
I don't really understand why this warning was thrown because I was
profiling the JVM with VisualVM and the JVM had plenty of heap space left.
Ayone any ideas?
Thanks, Jonck
On Tuesday, April 23, 2013 4:27:45 PM UTC+2, pm wrote:
Yeah no problem with ports, I can telnet 9200 and 9300 just fine.
Exception happens in middle of indexing documents
Thanks
Sent from my iPhone
On Apr 22, 2013, at 11:10 PM, David Pilato <da...@pilato.fr <javascript:>>
wrote:
Hard to say.
Did you open 9300 ports on your node instances?
--
David 
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 23 avr. 2013 à 01:09, pm <parmod...@gmail.com <javascript:>> a écrit :
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 into
Exception 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 client
ImmutableSettings.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 elasticsearc...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/0qM4YJvLeQE/unsubscribe?hl=en-US
.
To unsubscribe from this group and all its topics, send an email to
elasticsearc...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.
--
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.