ES is unable to transport an exception back to the client, exceptions are thrown, passed back and forth, and the procedure is retried until the Java stack is full (StackOverflowError). Yes, it is a concern, it is a bug, a stack overflow must not happen.
Is the gist the whole stack trace? I bet you only posted the first few lines... In the meantime, can you check if you run the same JVM version at server and client side? A transport exception can not be deserialized, and this is typical for a JVM mismatch. 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/CAKdsXoH37nkrvCOdfqpYP_sDD-ChmpiipWLb%3DgMe15LfttUv4w%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
