ES TransportClient uses a RetryListener which is a bit flaky in case of exceptions caused by faulty nodes. Some users reported an explosion of port use and connection retries, and this may also bring the client memory to a limit. Maybe you have stack traces that show abnormal behavior so it's worth to raise a github issue?
Jörg -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHbhiwkCmkKdu_4x7f6S28pmC35detFcXyaDDg9Dkjrkg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
