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

Vespa Installation Issue on Ubuntu 16.04 #3882

Closed
ankitjani opened this issue Oct 25, 2017 · 16 comments
Closed

Vespa Installation Issue on Ubuntu 16.04 #3882

ankitjani opened this issue Oct 25, 2017 · 16 comments
Labels
Projects

Comments

@ankitjani
Copy link

Hi,

How to install vespa in ubuntu?

As i gone through readme document. In that i have executed "docker/build-vespa.sh". But it's downloading CentOS files and due to this i am not able to use vespa. I have tried to find this things on google but I was not able to find the source of Vespa for Ubuntu and also not able to find any other packaes of Vespa for Ubuntu.

Kindly help me to resolve this issue or provide me the url where I can find the Installable of Vespa for Ubuntu.

Thanks.

@bratseth
Copy link
Member

We don't provide images for Ubuntu. I guess it wouldn't be too hard to do I guess somebody would need to contribute it as we don't use Ubuntu. Perhaps you can do it?

Otherwise I suggest running Vespa inside a Docker image.

@ankitjani
Copy link
Author

ankitjani commented Oct 30, 2017

Not an issue @bratseth. I have used Vespa inside a Docker image. Thanks for the Quick Response.
In below line,
"curl -s --head http://localhost:8080/ApplicationStatus"
What is this "ApplicationStatus". Is it any project which runs under vespa engine ?
Above command is not giving me 200 OK result.
So, i was little bit confused. How can i resolve this? Please let me know if you have any suggestions for the same.
How can i start vespa-engine separately ?

Thanks

@bratseth
Copy link
Member

Is it any project which runs under vespa engine

It's a built-in API which provides information about status of the deployed application.

If you don't get 200 OK it means the server did not come up.
Run
vespa-logfmt
to check the log.

@ankitjani
Copy link
Author

Yeah, Great!.
Now i got the 200 OK respone.
And i am able to run the Vespa 👍 .

Is there any way to connect the database?
I mean, i need to connect to the database(e.g. cassandra). So, is there any configuration i need to do in any project of vespa-engine?

@bratseth
Copy link
Member

We don't provide any Cassandra integration. Either PUT the documents one by one over HTTP, or, if you need high throughput use the Java HTTP client - http://docs.vespa.ai/documentation/vespa-http-client.html

@ankitjani
Copy link
Author

ankitjani commented Nov 1, 2017

Thanks for the quick response @bratseth .

java -jar $VESPA_HOME/lib/jars/vespa-http-client-jar-with-dependencies.jar --file feed.json --host localhost --port 8080

While executing above commange i am getting below error:
"Nov 01, 2017 4:48:27 PM com.yahoo.vespa.http.client.core.communication.IOThread cycle
INFO: Handshake did not work out localhost:8080 ssl=false"

i have deployed that "http-api-using-searcher" project and also build vespa-engine as well.
did i missed anything?
Please provide me some suggestion for the same.

@bratseth
Copy link
Member

bratseth commented Nov 1, 2017

Are there any warnings/errors in the log when you start? Check with
logfmt -l warning,error

Does it work to write single documents using the simple HTTP API as described here?:
http://docs.vespa.ai/documentation/document-api.html

@jobergum
Copy link
Member

jobergum commented Nov 1, 2017

The exact instructions in all our sample applications is tested by our build pipeline https://travis-ci.org/vespa-engine/documentation so most likely reason is that nothing runs on localhost:8080, can you telnet to it?

@ankitjani
Copy link
Author

ankitjani commented Nov 1, 2017

Yes, i am able to get the response from localhost:8080. But, Error remains the same while executing that command.

@bratseth
Copy link
Member

bratseth commented Nov 1, 2017

You mean telnet response or did you try the things I mentioned above?

@ankitjani
Copy link
Author

Yes, i am talking about telnet response.

@jobergum
Copy link
Member

jobergum commented Nov 1, 2017

If you search for 'http-api-' in https://s3.amazonaws.com/archive.travis-ci.org/jobs/295691361/log.txt?X-Amz-Expires=29&X-Amz-Date=20171101T124053Z&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJRYRXRSVGNKPKO5A/20171101/us-east-1/s3/aws4_request&X-Amz-SignedHeaders=host&X-Amz-Signature=a1d43b266d5b4230009588a6df8d2c071c8e3171be71a04760292880eb9173a2 you'll see how we test and execute the README.md for that particular sample application available here https://github.com/vespa-engine/sample-apps/tree/master/http-api-using-searcher so we know that these sample apps works.

vespa-logfmt (http://docs.vespa.ai/documentation/reference/logfmt.html) from inside the running docker container might give a hint about what's going on and if you are talking to a vespa or something else with forwarded to port 8080.

@ankitjani
Copy link
Author

ankitjani commented Nov 6, 2017

All the issues has been resolved and everything is UP and Running.
Thanks for the Support!

I just want to know that,
According to the sample-apps examples, It always search/feed and work using particular " *.json " file. If i want to change that it search from the database.. What should i need to do ?

How vespa search the data from external database ?
Is there any way to achieve this scenario ?

Please suggest me the way for the same.
Thank You!

@jobergum
Copy link
Member

jobergum commented Nov 6, 2017

You will need to export the data from the database, convert your DB schema to a Vespa document schema and index the data into Vespa using Vespa's json feed format.

@ankitjani
Copy link
Author

Okay. So, is there any option available to convert my DB schema to a Vespa document schema ?

@jobergum
Copy link
Member

jobergum commented Nov 6, 2017

There is currently no tool that will automatically convert your DB schema to a Vespa schema no.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Support
Awaiting triage
Development

No branches or pull requests

3 participants