CODEWITHSUNDEEP
vespa
Yash Kasat
Yash Kasat

Reputation: 203

How to setup vespa nodes for High availability

I have to deploy the Vespa database and the requirement is that it should be highly available. I have 3 instances available for the database. I have successfully deployed the database where 1 instance had config node, container node, and content node and the rest 2 instances had container node and config node. Redundancy was kept as 3 and searchable copies are also 3. But the issue here is if the instance with config node stops due to any reason then the whole system is unavailable.

So to avoid this, I was trying to have a config node on all the instances. But didn't able to deploy it successfully.

Link that I referred: https://docs.vespa.ai/en/reference/services-admin.html

<admin version="2.0">
    <adminserver hostalias="admin0"/>
    <configservers>
        <configserver hostalias="admin0"/>
        <configserver hostalias="admin1"/>
        <configserver hostalias="admin2"/>
    </configservers>
</admin>

What is that I am doing wrong here?

Also, is there a better way to ensure availability in Vespa, Please do let me know?

Thanks in Advance

Upvotes: 2

Views: 400

Answers (1)

Kristian Aune
Kristian Aune

Reputation: 981

Please note that the documents are stored on the content nodes, so you need three of those, too. So maybe just set up config, container and content on all nodes?

Upvotes: 1

Related Questions