This usually means that there is no local server bound to that port. If you're performing an integration test, it could be that you aren't giving ES time to completely initialize and bind to the port and be ready to accept connections. Or that you aren't configuring your local node to be a server so it's not binding to the port to which you wish to connect.
I don't know the deterministic way to wait for ES to be listening to its ports, so one of my production servers (that uses a TransportClient and contains our business logic) waits 4 seconds for ES to start up, and then waits for the Yellow status (at least) before it starts. That has never failed to start-up properly, probably due to the TransportClient retrying the initial connection if it's not yet available during the wait for yellow status. Perhaps? Your colleague's case is successful when connecting to another host because more than likely ES is already up and running on that other host. Brian -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/ec9ac253-236e-4ad2-b37b-d63e5030e018%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
