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
Crashing with "panic: failed to migrate ds" #4588
Comments
Hi @shashank42 , thank you for reporting the issue. I will get back to you soon. |
@shashank42 can you please share the version number of |
For the current deployment
https://github.com/glip-gg/rudderstack-helm Here is the repo I am using |
I think the issue is similar to this. I have taken the steps here, that is deleting all the tables inside jobsdb, however the errors have not stopped |
@shashank42 does the issue persist when you restart the postgres db pod? |
@shashank42 can you check the resource (CPU, RAM) usage before and after you start the server? please also mention what resources(CPU, memory) have you provisioned for postgres? Context: with the limited info, we are guessing that enough resources might not have been allocated (assuming the server is not overloaded with unusual number of requests) which causes a query timeout |
@shashank42 can you please help with more information as mentioned above? |
Describe the bug
Deployed using https://github.com/rudderlabs/rudderstack-helm
rudderstack backend keeps crashing and restarting with the error
While at the same time postgress machine logs the following error
While there are no errors on transformer
The text was updated successfully, but these errors were encountered: