1

I am using vespa as a database for some application. It was running perfectly okay and suddenly stops working. When checked with command vespa-get-cluster-state it returned the result as shown below: enter image description here

But when I checked with command vespa-config-status it return the result as shown below: enter image description here

To rectify this type of issue, I have to again deploy the application using vespa-deploy prepare application.zip && vespa-deploy activate and then restart all the services.

But I need to know the reason why the database stops suddenly. And how to handle this issue to make sure it won't happen again.

Yash Kasat
  • 203
  • 1
  • 5

1 Answers1

2

By stopped working what do you mean? You mean the port 8080 of the stateless container has stopped listening? There are multiple services making up one running Vespa instance and the socket write error could indicate that the container is no longer listening for some reason.

vespa-logfmt inside the docker container could tell you why.

Jo Kristian Bergum
  • 2,984
  • 5
  • 8