Another thought: TransportSerializationException can also occur if a custom
Java class is present that generates custom exceptions. Maybe you use
plugins on the cluster nodes but not the same plugin code on the client? If
so, the client can't deserialize the custom exception.

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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHUdYEUP3Qft7B8pYsuz2dE13ib%3DPQ2nH5ZEVgwsBpB0A%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to