I was doing a test with elastic search and heavy indexing and I left the
system running overnight. The system is two ES data nodes in cluster and
one TransportClient that is shared between threads in a Web Application.
The Web Application does the heavy indexing.
In the morning, I saw that the indexing finished successfully but when I
was trying to do queries or even check the status using the AdminClient
interface from the same single instance of TransportClient (it was still
the same instance used for indexing) I always got a "... disconnected"
exception. The ES data nodes in the cluster were working perfectly. I had
to restart the Web App (so the TransportClient was recreated) to be able to
connect again to the data nodes and do the queries and all that.
I was really surprised that the TransportClient didn't try to recreate the
connection to recover its own state. If you plan to use a singleton
TransportClient shared between requests and only close when the whole App
is being shutdown, the self-recovery should be a must in TransportClient.
Am I missing something with the TransportClient configuration or is there
another client variant to handle reconnection automatically?
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.
For more options, visit https://groups.google.com/groups/opt_out.