-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
v5 connect panic: no Elasticsearch node available #387
Comments
One word: Sniffing. The client will try to find other nodes in the cluster by default (as all official Elasticsearch clients do). It will do so by finding the Either disable sniffing ( |
I followed Connection-Problems on Wiki, but still get "no Elasticsearch node available" Which version of Elastic are you using?
Please describe the expected behaviorpanic: no Elasticsearch node available Please describe the actual behavior
Any steps to reproduce the behavior?Run the code above |
Works fine here. I set up an example here a few months ago: https://gist.github.com/olivere/d49cae8646122d163103e4c12cc2d66a. That works fine here. You need to make sure that the server (the part which runs the Elastic code) can connect to 127.0.0.1:9200. That's all that's required. |
I also added a simple connect example.
|
Thanks for quick response. I tested your example and simple connect. Do I need something if it works on top of Google App Engine? |
@kuma-guy There's a wiki page for that. |
@olivere it works! sorry for taking your time and thanks for your help! |
elastic.SetSniff(false) |
@478682649 Thinking of making this the official slogan of the library: "elastic.SetSniff(false) is a Go library for Elasticsearch" ;-) |
I try to use the following command to have a quick start of carley |
@ZChristine You can disable health checks alongside with sniffing. Something like this:
If you want to know how to configure Elasticsearch in a way that you don't need to do this, see https://github.com/olivere/elastic-with-docker. |
@ZChristine Maybe this is an issue for Cayley, as they don't seem to support passing parameters into Elastic. I wonder if they could use the |
thanks for timely replying . I got the wrong way of command prompt before , and I fixed it later. And download the nq file into local elastic . But the loading speed is pretty slow, was this because of the way that es storage the data from cayley ? If the data was like triple model, what does it look like in es? |
Elasticsearch Bulk API is pretty fast. It depends on various factors though, e.g. the size of the documents or the I/O of the cluster. You should really talk to the authors of Cayley for those things. BTW I opened cayleygraph/cayley#730 to address the original issue you mentioned. |
thanks so much |
I have the same problem, I added |
Please use the following questions as a guideline to help me answer
your issue/question without further inquiry. Thank you.
Which version of Elastic are you using?
[ ] elastic.v5 (for Elasticsearch 5.x)
Please describe the expected behavior
panic: no Elasticsearch node available
Please describe the actual behavior
Any steps to reproduce the behavior?
Run the code above
The text was updated successfully, but these errors were encountered: