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
Error connecting (?) to ES #14
Comments
Hi @rodrigoalviani , The log says that :
This issue is not related with mongolastic. Default transport port of es is 9300. |
Hi @ozlerhakan, Locally I connect to ES on 9200, where its is set? |
Yes, but mongolastic communicates through es's tcp transport port. |
do you solve your issue? @rodrigoalviani |
@ozlerhakan |
hello, I am sorry to tell that, but I have exactly the same problem :
My config file
if it can helps I use ElasticSeach 5.5 |
Hi @MaxCreeger32 , Which auth do you use in your mongod? it says that |
sorry, yes I have seen that problem that is solved now : but I still have the ElasticSearch connection problem :
|
Have you looked at these threads: https://stackoverflow.com/questions/25912572/java-elasticsearch-none-of-the-configured-nodes-are-available , https://stackoverflow.com/questions/42826735/nonodeavailableexception-none-of-the-configured-nodes-are-available?rq=1 you may need to specify a cluster name in the mongolastic config file:
|
thanks for the links !
and the cluster name in my elastic search is correct :
but I still have :
as i see in your code, it seems to be somewhere in the elastic packages not yours ... i do not understand why I still have this error. |
hmm, which version of mongolastic do you use? could you try previous jar files? maybe this is a problem for the latest jar |
It seems to be the version 1.4.3 as the indication in the link is : https://github.com/ozlerhakan/mongolastic/releases/download/v1.4.3/mongolastic.jar |
oh i just see in the release that there is a new one ! I will test with this one |
It seems that the version 1.4.2 is OK ! 👍 |
thanks for all your support |
I have just seen that in tyhe histry of ElasticConfiguration.java :
may be it is the TransportAdress class that have a problem in comparison of the InetSocketTransportAddress |
Great @MaxCreeger32 ! good to hear that it works with 1.4.2 :)
Hmm, if we have another case for that issue, I'll look a solution |
Hi!
My error looks like:
|
My config file:
Error:
The text was updated successfully, but these errors were encountered: