Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ddprofiler throws RemoteTransportException with elasticsearch v2.3.5 #54

Closed
jmftrindade opened this issue Aug 24, 2016 · 1 comment
Closed

Comments

@jmftrindade
Copy link
Member

Noticed today while running ddprofiler against my local installation of elasticsearch 2.3.5. The ddprofiler server started throwing the following exception:

org.elasticsearch.transport.RemoteTransportException: [Failed to deserialize response of type [org.elasticsearch.action.admin.cluster.node.liveness.LivenessResponse]]

This only happens after commit 0ee4a9a - Merge algebra into master. I'm guessing because of the transport changes on the store client?

Workaround: I downgraded to elasticsearch v2.3.0 as per requirements.txt, and then it works fine.

@raulcf
Copy link
Contributor

raulcf commented Aug 24, 2016

I'm guessing because of the transport changes on the store client?

I think so. I think if we change the storeClient from the native (the current one that causes trouble in 2.3.5) to the REST-based one it should work just fine.

The elastic people indicate that it is not guaranteed that native clients work across versions:

https://www.elastic.co/blog/found-interfacing-elasticsearch-picking-client#transport-client

Since the native client performs a bit better, I'd keep the native as default and probably add a property to configure the storeClient one wants.

@raulcf raulcf closed this as completed Sep 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants