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

Elastic4s for es 2.4.x #647

Closed
avdv opened this issue Oct 17, 2016 · 5 comments
Closed

Elastic4s for es 2.4.x #647

avdv opened this issue Oct 17, 2016 · 5 comments

Comments

@avdv
Copy link
Contributor

avdv commented Oct 17, 2016

I haven't tried yet, and I'm a bit weary... but does elastic4s 2.3.1 also work with es 2.4.x?

Otherwise could you prepare a release? Thanks!

@jmleoni
Copy link

jmleoni commented Oct 17, 2016

From what we could test on our setup it doesn't always work with 2.4
👍 for this one

@avdv
Copy link
Contributor Author

avdv commented Oct 18, 2016

@jmleoni which problems have you run into when trying the 2.4?

Currently we are facing NoNodeAvailableException: None of the configured nodes are available: [{#transport#-1}{127.0.0.1}{localhost/127.0.0.1:9300}] using 2.3.4 which is probably just a "concealed" ClientStoppedException (elastic/elasticsearch#18708) and es 2.4.x has this fixed.

@jmleoni
Copy link

jmleoni commented Oct 18, 2016

Well, the thing is, I have little detail, as the setup where the problem was has been destroyed.
It had to do with the transportClient though. I need to retest to be sure. it should be done by next week. I will let you know in deeper details if we encounter the problem again.

@sksamuel
Copy link
Collaborator

I'll try and release a 2.4 tonight, been focusing on 5.0

On 18 October 2016 at 09:02, Jean-Marc Leoni notifications@github.com
wrote:

Well, the thing is I had little detail, has the setup where the problem
was has been destroyed.
It had to do with the transportClient though. I need to retest to be sure.
it should be done by next week. I will let you know in deeper details if we
encounter the problem again.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#647 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAtZGnCuRcnNNd834FJVoteZBUZSEc5Mks5q1H0CgaJpZM4KYkw3
.

@sksamuel
Copy link
Collaborator

I've just released this, sorry for the delay.

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

3 participants