kkraune
commented
3 years ago log messages like
[2021-06-10 09:27:39.927] WARNING : logd logdemon.vespalib.net.async_resolver could not resolve host name: 'vespa-admin.vespa-net'
[2021-06-10 09:27:39.928] WARNING : slobrok vespa-slobrok.vespalib.net.async_resolver could not resolve host name: 'vespa-configserver-b.vespa-net'means that something is wrong with the network configuration, so all the hosts cannot talk to each other. I think you must resolve this problem first. please make sure by logging into a nodes and ping the other nodes by name, and configure network accordingly (hostname files etc)
you can review https://github.com/vespa-engine/sample-apps/tree/master/basic-search-on-docker-swarm as well, it looks similar to this
yashkasat96
I had a requirement where I have to deploy the highly available Vespa database on 3 instances. What I need is if any of the 2 instances are down then also the database should be able to add, delete, update, read and search on whole data.
I have deployed Vespa using docker containers. 3 contains created on 3 different instances. To make it highly available I made all the instances as config node, container node, and content node.
The configuration (service.xml) that I am using is.
The commands that I have been using to create a docker container are mentioned below. Instance-A:
docker run --detach --privileged --name vespa-admin --hostname vespa-admin.vespa-net --network=vespa-net --env VESPA_CONFIGSERVERS=vespa-admin.vespa-net,vespa-configserver-a.vespa-net,vespa-configserver-b.vespa-net --restart unless-stopped <other-arguments> vespaengine/vespaInstance-B:
docker run --detach --privileged --name vespa-configserver-a --hostname vespa-configserver-a.vespa-net --network=vespa-net --env VESPA_CONFIGSERVERS=vespa-admin.vespa-net,vespa-configserver-a.vespa-net,vespa-configserver-b.vespa-net --restart unless-stopped <other-arguments> vespaengine/vespaInstance-C:
docker run --detach --privileged --name vespa-configserver-b --hostname vespa-configserver-b.vespa-net --network=vespa-net --env VESPA_CONFIGSERVERS=vespa-admin.vespa-net,vespa-configserver-a.vespa-net,vespa-configserver-b.vespa-net --restart unless-stopped <other-arguments> vespaengine/vespaNow when I deploy the application it gives out this:
Is any of this log info need to be handled so that it won't create any problem?
When I stop any 1 of the instances the request (add, update, delete, read and search) is processed on the other two nodes successfully. But when I try to stop any of the 2 instances simultaneously then I am not able to get a response for the requests(add, update, read, delete) and also the inactive records in that instances didn't get active.
The logs from the command vespa-logfmt -l warning,error is shown below.
And also was not able to connect to the zookeeper using 'bash /opt/vespa/bin/vespa-zkcli'.
What should I do to make it highly available system. That is if any 2 of the nodes becomes inactive due to some reason then also the system should be available for all the operations.