Open sahirshahs opened 1 year ago
Hi,
This specific error is a "downstream" error of something else happened earlier, usually a restart of the server/node is enough to clean up this error, if nothing else major has happened, the 3.2.2 version is quite back in time now, we do suggest to update to the last hotfix ( at time of writing 3.2.17), there have been quite a lot of fixes in the meanwhile that avoid this error to happen with recent versions.
So feel free to update to the last hotfix and report if you still experience similar problems.
Regards
OrientDB Version: 3.2.2 base image in kubernetes container
Java Version: Orientdb 3.2.2 base image running on container
OS: Kubernetes running on Linux
Expected behavior
OrientDb started throwing internal server error, scriptexecutiontimeout error, restart error etc and stopped working. Repair database command not detecting any error. 2 different types of error messages logged in the db console attached here. Please help on this issue. Similar issue came on multiple instance of our testing and production critically. It would be helpful if someone can help on this issue to recover and also to prevent in future.
Actual behavior