I posted earlier with an issue that I spent quite a bit of time trying to
figure out how to setup EC2 cluster, I followed documentation, but still
couldn't get it to work, I have 2 "i.4xlarge instances"
So, I decided to sale down the problem and work with one instance:
I installed the latest 1.0.0 on EC2 instance and "aws plugin 2.0", the
instance works fine from http API but not from my Java/API transport client.
Note, the transport client works fine against my local ES server (0.90.9),
so nothing wrong with the Java client.
Settings settings = ImmutableSettings.settingsBuilder()
.put("refresh_interval", "-1") //Needs to be updated after indexing is
.put("client.transport.ping_timeout", "10s") //Node conn timeout
But when I use My JavaAPI/Transport Client against Version 1.0.0 on the
instance, I get this error:
WARN - Log4jESLogger.internalWarn(124) | [The Stepford Cuckoos] Message not
fully read (response) for  handler
error [true], resettingException in thread "main"
org.elasticsearch.client.transport.NoNodeAvailableException: No node
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 firstname.lastname@example.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/d0ecf9ca-619d-4127-b534-01147d829a79%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.